2 |
Approval of the agenda |
|
R4-2200001 |
RAN4#101-e Meeting Report |
ETSI MCC |
R4-2200002 |
Agenda for RAN4#101-bis-e |
RAN4 Chair (Huawei) |
R4-2200003 |
RAN4#101-bis-e E-Meeting Arrangements and Guidelines |
RAN4 Chair (Huawei) |
R4-2202424 |
RRM session Chair notes |
Vice Chair (Intel) |
R4-2202425 |
BSRF_Demod_Testing session Chair notes |
Vice Chair (Samsung) |
3 |
Letters / reports from other groups / meeting |
|
R4-2200005 |
LS on Energy Efficiency as guiding principle for new solutions |
SA |
R4-2200006 |
Reply LS on inclusion of the 6425-7125 MHz frequency band in the 3GPP specification for 5G-NR/IMT-2000 systems |
RAN |
R4-2200007 |
LS on updates to study on optimizations of pi/2 BPSK uplink power in NR |
RAN |
R4-2200008 |
Liaison statement to 3GPP TSG RAN on the inclusion of the 6425-7125 MHz frequency band in the 3GPP specification for 5G-NR / 1MT-2020 systems |
RCC Commission on Spectrum and Satellite Orbits |
R4-2200009 |
Reply LS to RP-211577 on Test methods for over-the-air Total Radiated Power (TRP) field measurements of unwanted emissions from IMT radio equipment utilizing active antennas |
ITU-R WP1C |
R4-2200010 |
LS on work towards two new recommendations "Generic unwanted emission characteristics of base / mobile stations using the terrestrial radio interfaces of IMT-2020 |
RAN5 |
R4-2200011 |
LS on configuration of p-MaxEUTRA and p-NR-FR1 |
RAN5 |
R4-2200012 |
Reply to LS (in R4-2120025) on FR2 UE relative power control tolerance requirements |
RAN5 |
R4-2200013 |
Reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 |
RAN3 |
R4-2200014 |
LS on TRS-based SCell activation details |
RAN2 |
R4-2200015 |
LS response on PC5 DRX for ProSe |
RAN2 |
R4-2200016 |
Reply LS on signalling for intra-band CA with UL-MIMO |
RAN2 |
R4-2200026 |
Reply LS on R17 NR MG enhancements – Concurrent MG |
RAN2 |
R4-2200027 |
Response LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e |
RAN2 |
R4-2200028 |
Reply LS on the use of NCD-SSB instead of CD-SSB for RedCap UEs |
RAN2 |
R4-2200029 |
Reply LS to RAN4 on UL gap in FR2 RF enhancement |
RAN2 |
R4-2200030 |
LS to RAN4 on L3 filter configuration |
RAN2 |
R4-2200031 |
Reply LS on specification impact for methods on efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
RAN2 |
R4-2200032 |
LS on MPE information signalling |
RAN2 |
R4-2200033 |
Reply LS on Pre-configured MG |
RAN2 |
R4-2200034 |
LS on the minimum time gap for wake-up and Scell dormancy indication for NR operation in 52.6 to 71 GHz |
RAN1 |
R4-2200035 |
Follow-up reply LS on inter-cell beam management and multi-TRP in Rel-17 |
RAN1 |
R4-2200036 |
LS on DL PRS processing by UEs in RRC_INACTIVE state |
RAN1 |
R4-2200037 |
LS on UL SRS-RSRPP definition |
RAN1 |
R4-2200038 |
Reply LS on capability related RAN2 agreements for RedCap |
RAN1 |
R4-2200040 |
LS on L1-RSRP measurement behaviour when SSBs associated with different PCIs overlap |
RAN1 |
R4-2200041 |
LS on lower Rx beam sweeping factor for latency improvement |
RAN1 |
R4-2200042 |
LS on DL synchronization enhancements for IoT NTN |
RAN1 |
R4-2200043 |
LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#107-e |
RAN1 |
R4-2200044 |
LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE |
RAN1 |
R4-2200045 |
LS on sensing beam selection |
RAN1 |
R4-2200046 |
LS on BFR for CORESET with two activated TCI states |
RAN1 |
R4-2200047 |
LS on propagation delay compensation |
RAN1 |
R4-2200048 |
LS on Rel-17 MAC-CE impacts |
RAN1 |
R4-2200049 |
Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure |
RAN1 |
R4-2200050 |
Reply LS on initial state of elements controlled by MAC CEs |
RAN1 |
R4-2200051 |
LS on the condition of PRS measurement outside the MG |
RAN1 |
R4-2200052 |
LS on updated Rel-17 RAN1 UE features list for LTE |
RAN1 |
R4-2200053 |
LS on updated Rel-17 RAN1 UE features list for NR |
RAN1 |
R4-2200054 |
LS on the reporting of the Tx TEG association information |
RAN1 |
R4-2200055 |
LS on channel quality reporting for NB-IoT |
RAN1 |
R4-2200056 |
LS on range of power control parameters for eIAB |
RAN1 |
R4-2200057 |
LS on updated Rel-17 LTE and NR higher-layers parameter list |
RAN1 |
R4-2200058 |
LS on triggering signalling of temporary RS for SCell activation |
RAN1 |
R4-2202053 |
Reply LS on HO with PSCell from NR SA to EN-DC |
RAN2 |
4 |
Rel-17 feature list |
|
R4-2200286 |
Initial views on R17 feature list |
Apple |
R4-2200485 |
Inputs to Rel-17 NR UE features for measurement gap enhancement |
MediaTek inc. |
R4-2200544 |
Discussion on Rel-17 RAN4 UE feature list |
Intel Corporation |
R4-2200641 |
Discussion on UE capability for FR1 HST enhancement |
CMCC |
R4-2201446 |
Initial review of RAN4 UE feature in Rel-17 |
ZTE Corporation |
R4-2201803 |
A new Rel-17 per-FR MG capability based on Per BC |
Qualcomm Incorporated |
R4-2202239 |
Email discussion summary for [101-bis-e][139] R17_feature_list |
Moderator (CMCC) |
R4-2202339 |
Email discussion summary for [101-bis-e][139] R17_feature_list |
Moderator (CMCC) |
R4-2202400 |
Rel-17 UE feature list |
CMCC |
R4-2202401 |
LS on Rel-17 RAN4 UE features list for NR |
CMCC |
5.1.1 |
General |
|
R4-2200429 |
Overview of the Region 1 countries implementing lower 6GHz unlicensed band |
Apple |
R4-2201080 |
draft TR 38.849 v0.6.0 |
Nokia, Nokia Shanghai Bell |
R4-2202201 |
Email discussion summary for [101-bis-e][101] NR_6GHz_unlic_EU |
Moderator (Nokia) |
R4-2202249 |
WF on introduction of lower 6GHz NR unlicensed operation |
Nokia |
R4-2202250 |
WF on adding a 20 MHz channel opportunity (Channel and Sync raster point) in the 5925-5945 MHz range for n96 and n102 |
Apple |
R4-2202301 |
Email discussion summary for [101-bis-e][101] NR_6GHz_unlic_EU |
Moderator (Nokia) |
R4-2202421 |
draft TR 38.849 v0.6.0 |
Nokia, Nokia Shanghai Bell |
5.1.2 |
Band definition and channel arrangement |
|
R4-2200910 |
On channel rasters for the 6GHz unlicensed band |
Apple |
R4-2201081 |
On band definition for the lower 6GHz NR unlicensed operation |
Nokia, Nokia Shanghai Bell |
5.1.3 |
UE RF requirements |
|
R4-2200430 |
Introduction of the lower 6GHz unlicensed band |
Apple, Skyworks Solutions Inc., MediaTek Inc. |
R4-2200849 |
Unwanted emissions requirements for lower 6GHz NR unlicensed operation for Europe |
Ericsson |
R4-2200850 |
Unwanted emissions requirements for Band n102 |
Ericsson |
R4-2201854 |
NS signaling, MPR, and A-MPR for the 5925 – 6425 MHz NR-U band |
Qualcomm Incorporated |
5.1.4 |
BS RF requirements |
|
R4-2201082 |
Running CR for 38.104 to add n102 |
Nokia, ZTE Corporation |
R4-2201474 |
Discussion on MU for EU band n102 |
ZTE Corporation |
R4-2201475 |
draft CR to TS38.141-2 the introduction of EU unlicensed band n102 |
ZTE Corporation |
R4-2201476 |
draft CR to TS36.104 the introduction of EU unlicensed band n102 |
ZTE Corporation |
R4-2201918 |
draft CR 37.105 on Introduction of lower 6GHz NR unlicensed operation for Europe |
Ericsson |
R4-2201928 |
draftCR to 37.145-1 - adding band n102 |
Huawei |
R4-2201929 |
draftCR to 37.145-2 - adding band n102 |
Huawei |
R4-2201998 |
draft CR to 37.104 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
5.1.5 |
Others |
|
R4-2200431 |
TP for TR 38.849 |
Apple |
R4-2201083 |
TP to TR 38.849 updating clause 5.1 for the lower 6GHz band |
Nokia, Nokia Shanghai Bell |
R4-2202001 |
draft CR to 37.141 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2202002 |
draft CR to 36.141 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2202251 |
Introduction of the lower 6GHz unlicensed band |
Apple, Skyworks Solutions Inc., MediaTek Inc. |
R4-2202252 |
Running CR for 38.104 to add n102 |
Nokia, ZTE Corporation |
R4-2202253 |
draft CR to TS38.141-2 the introduction of EU unlicensed band n102 |
ZTE Corporation |
R4-2202254 |
draft CR to TS36.104 the introduction of EU unlicensed band n102 |
ZTE Corporation |
R4-2202255 |
draft CR 37.105 on Introduction of lower 6GHz NR unlicensed operation for Europe |
Ericsson |
R4-2202256 |
draftCR to 37.145-2 - adding band n102 |
Huawei |
R4-2202257 |
draft CR to 37.104 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2202258 |
TP for TR 38.849 |
Apple |
R4-2202259 |
draft CR to 37.141 on introduction of n102 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2202422 |
Introduction of the lower 6GHz unlicensed band |
Apple, Skyworks Solutions Inc., MediaTek Inc. |
5.2 |
Introduction of operation in full unlicensed band 5925-7125MHz for NR |
|
R4-2202202 |
Email discussion summary for [101-bis-e][102] NR_6GHz_unlic_full |
Moderator (Apple) |
R4-2202302 |
Email discussion summary for [101-bis-e][102] NR_6GHz_unlic_full |
Moderator (Apple) |
5.2.1 |
General |
|
R4-2200432 |
Update of the 6GHz unlicensed band system and regulatory requirements in Region 2 and Region 3 countries |
Apple |
R4-2201084 |
On band definition for 6GHz NR unlicensed operation |
Nokia, Nokia Shanghai Bell |
R4-2202260 |
WF on introduction of the full unlicensed band |
Apple |
5.2.2 |
Regulatory requirements and evaluation for re-using existing NS |
|
R4-2200374 |
Introduction of the VLP mode for the 6GHz unlicensed band |
TTA |
R4-2200433 |
Applicability of band n96 |
Apple |
5.2.3 |
UE RF requirements |
|
R4-2200434 |
Draft CR for TS 38.101-1 |
Apple |
R4-2201125 |
Discussion on the impact of the New power class definitions for NR-U UE in other countries |
LG Electronics Inc. |
R4-2201128 |
A-MPR analysis results for NR-U(VLP) considering regulatory parameters in Korea |
LG Electronics Inc. |
R4-2202261 |
A-MPR analysis results for NR-U(VLP) considering regulatory parameters in Korea |
LG Electronics Inc. |
R4-2202262 |
Draft CR for TS 38.101-1 |
Apple |
5.2.4 |
BS RF requirements |
|
R4-2201515 |
TP for BS RF requirements |
Huawei, HiSilicon |
5.2.5 |
Others |
|
R4-2200435 |
TP for TR 38.849 |
Apple |
R4-2201085 |
TP to TR 38.849 updating clause 5.1 for the full 6GHz band |
Nokia, Nokia Shanghai Bell |
R4-2202263 |
TP for TR 38.849 |
Apple |
R4-2202264 |
TP to TR 38.849 updating clause 5.1 for the full 6GHz band |
Nokia, Nokia Shanghai Bell |
5.3 |
Introduction of 6GHz NR licensed bands |
|
R4-2202203 |
Email discussion summary for [101-bis-e][103] NR_6 GHz_licensed |
Moderator (Huawei) |
R4-2202303 |
Email discussion summary for [101-bis-e][103] NR_6 GHz_licensed |
Moderator (Huawei) |
5.3.1 |
General |
|
R4-2200436 |
Initial considerations on requirements for the licensed operation in the upper 6GHz frequency range |
Apple |
R4-2201231 |
Discussion on general issues for 6GHz licensed band |
CATT |
R4-2201330 |
6GHz licensed band - General |
Ericsson |
R4-2201503 |
General aspects for 6GHz NR licensed band |
Huawei, HiSilicon |
R4-2201987 |
6GHz licensed band aspects |
MediaTek (Chengdu) Inc. |
R4-2202265 |
WF on general aspects for 6GHz licensed band |
Huawei, HiSilicon |
R4-2202266 |
WF on system parameters for 6GHz licensed band |
ZTE |
R4-2202267 |
WF on UE RF requirements for 6GHz licensed band |
Ericsson |
R4-2202268 |
WF on BS RF requirements for 6GHz licensed band |
CATT |
R4-2202415 |
Further reply LS on inclusion of the 6425-7125 MHz frequency band in the 3GPP specification for 5G-NR/IMT-2000 systems |
Apple |
5.3.2 |
System parameters |
|
R4-2200149 |
Discussion on system parameters for 6GHz licensed band |
CATT |
R4-2200152 |
draft CR on introduction of 6GHz licensed band for 38.101-1 |
CATT |
R4-2201304 |
Discussion on system parameters for 6G license band |
Xiaomi |
R4-2201331 |
6GHz licensed band - BS requirements |
Ericsson |
R4-2201447 |
Discussion on system parameters for 6425-7125MHz |
ZTE Corporation |
R4-2201504 |
System parameters for 6GHz NR licensed band |
Huawei, HiSilicon |
R4-2201545 |
6GHz licensed band attributes based on RCC recommendations |
Skyworks Solutions Inc. |
R4-2201824 |
draft CR on introduction of 6GHz system parameters for 38.101-1 |
ZTE Corporation |
R4-2201825 |
draft CR on introduction of 6GHz system parameters for 38.104 |
ZTE Corporation |
5.3.3 |
UE RF requirements |
|
R4-2200150 |
Discussion on UE RF requirements for 6GHz licensed band |
CATT |
R4-2201305 |
Discussion on UE RF requirements for 6G license band |
Xiaomi |
R4-2201332 |
6GHz licensed band - UE requirements |
Ericsson |
R4-2201448 |
Discussion on UE RF requirements for 6425-7125MHz |
ZTE Corporation |
R4-2201505 |
UE RF requirements |
Huawei, HiSilicon, CMCC, China Unicom, OPPO |
R4-2201506 |
Draft CR for 38.101-1: 6GHz NR licensed band |
Huawei, HiSilicon,CMCC, China Telecom, China Unicom, OPPO |
R4-2201826 |
draft CR on introduction of 6GHz UE RF requirements for 38.101-1 |
ZTE Corporation |
R4-2201855 |
6 GHz licensed band |
Qualcomm Incorporated |
5.3.4 |
BS RF requirements |
|
R4-2200153 |
Analysis on BS requirements for operation in 6GHz band |
CATT |
R4-2200154 |
draft CR on introduction of 6GHz licensed band for 38.104 |
CATT |
R4-2200155 |
draft CR on introduction of 6GHz licensed band for 38.141-1 |
CATT |
R4-2200156 |
draft CR on introduction of 6GHz licensed band for 38.141-2 |
CATT |
R4-2200157 |
draft CR on introduction of 6GHz licensed band for 37.104 |
CATT |
R4-2200158 |
draft CR on introduction of 6GHz licensed band for 37.105 |
CATT |
R4-2200159 |
draft CR on introduction of 6GHz licensed band for 37.141 |
CATT |
R4-2200160 |
draft CR on introduction of 6GHz licensed band for 37.145-1 |
CATT |
R4-2200161 |
draft CR on introduction of 6GHz licensed band for 37.141-2 |
CATT |
R4-2200480 |
draft CR on introduction of 6GHz licensed band for 38.174 |
CATT |
R4-2200481 |
draft CR on introduction of 6GHz licensed band for 38.176-1 |
CATT |
R4-2200482 |
draft CR on introduction of 6GHz licensed band for 38.176-2 |
CATT |
R4-2201449 |
Discussion on BS RF requirements for 6425-7125MHz |
ZTE Corporation |
R4-2201450 |
draft CR to TS38.104 the introduction of 6425-7125MHz |
ZTE Corporation |
R4-2201451 |
draft CR to TS36.104 the introduction of coexistence requirements of licensed band 6425-7125MHz |
ZTE Corporation |
R4-2201452 |
draft CR to TS36.141 the introduction of coexistence requirements of licensed band 6425-7125MHz |
ZTE Corporation |
R4-2201507 |
BS RF requirements |
Huawei, HiSilicon, China Unicom, CMCC |
R4-2201508 |
Draft CR for 38.104: 6GHz NR licensed band |
Huawei, HiSilicon |
R4-2201827 |
draft CR to TS 38.174 introduction of 6GHz coexistence requirement in IAB spec |
ZTE Corporation |
R4-2201828 |
draft CR to TS 38.176-1 on introduction of coexistence requirement for 6GHz |
ZTE Corporation |
R4-2201829 |
draft CR to TS 38.176-2 on introduction of coexistence requirement for 6GHz |
ZTE Corporation |
5.3.5 |
Others |
|
R4-2201453 |
Discussion on MR/LA BS UEM requirements for 6425-7125MHz and 10-10.5GHz |
ZTE Corporation |
R4-2201454 |
draft CR to TR38.921 MR and LA BS requirements for 6425-7125MHz and 10-10.5GHz |
ZTE Corporation |
5.4.1 |
General |
|
R4-2201687 |
Revised TR 38.853 version 0.2.0 |
Union Inter. Chemins de Fer |
R4-2202204 |
Email discussion summary for [101-bis-e][104] RAIL_900_1900MHz |
Moderator (UIC) |
R4-2202245 |
Revised TR 38.853 version 0.2.0 |
Union Inter. Chemins de Fer |
R4-2202304 |
Email discussion summary for [101-bis-e][104] RAIL_900_1900MHz |
Moderator (UIC) |
5.4.2 |
UE RF requirements |
|
R4-2200702 |
On RMR900 sensitivity |
Nokia |
5.4.3 |
BS RF requirements |
|
R4-2201324 |
RMR 900 MHz - BS RF |
Ericsson |
R4-2201325 |
Draft CR to TS 38.141-2: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2201326 |
Draft CR to TS 36.104: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2201327 |
Draft CR to TS 36.141: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2201689 |
TR_38.853_changes_clause 9 |
Union Inter. Chemins de Fer |
R4-2201805 |
Cross-check on the implementation of ECC Decision (20)02 for RMR900 |
Huawei |
R4-2201806 |
draft CR to TS 38.104: consideration of regional requirements for RMR900 |
Huawei |
R4-2201807 |
Remaining aspects for BS RF requirements for RMR900 |
Huawei |
R4-2201808 |
Draft CR to TS 38.104: RX requirements |
Huawei |
R4-2201809 |
TP to TR 38.853: BS RF requirements |
Huawei |
R4-2201810 |
Draft CR to TS 37.105: RMR implementation |
Huawei |
R4-2201811 |
Consideration of coordinated/un-coordinated deployments for the RMR900 requirements in RAN4 specifications |
Huawei |
R4-2201996 |
draft CR to 37.104 on introduction of n100 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2201999 |
draft CR to 37.141 on introduction of n100 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2202003 |
draft CR to 38.104 on introduction of n100 (system parameters) |
Nokia, Nokia Shanghai Bell |
R4-2202026 |
Draft CR to TS 37.145-1: RMR implementation |
Huawei |
R4-2202027 |
Draft CR to TS 37.145-2: RMR implementation |
Huawei |
R4-2202953 |
Email discussion summary for[101-bis-e][311] RAIL_900_1900MHz_BSRF |
Moderator (Ericsson) |
R4-2203049 |
Draft CR to TS 38.141-2: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2203050 |
Draft CR to TS 36.104: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2203051 |
Draft CR to TS 36.141: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2203053 |
TR_38.853_changes_clause 9 |
Union Inter. Chemins de Fer |
R4-2203054 |
Cross-check on the implementation of ECC Decision (20)02 for RMR900 |
Huawei |
R4-2203055 |
Draft CR to TS 38.104: RX requirements |
Huawei |
R4-2203056 |
TP to TR 38.853: BS RF requirements |
Huawei |
R4-2203057 |
Draft CR to TS 37.105: RMR implementation |
Huawei |
R4-2203059 |
draft CR to 37.104 on introduction of n100 and n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2203060 |
draft CR to 37.141 on introduction of n100 and n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2203061 |
draft CR to 38.104 on introduction of n100 and n101 (system parameters) |
Nokia, Nokia Shanghai Bell |
R4-2203062 |
WF on remaining aspects for BS RF requirements for RMR 900/1900 |
Ericsson |
R4-2203095 |
Email discussion summary for[101-bis-e][311] RAIL_900_1900MHz_BSRF |
Moderator (Huawei) |
R4-2203125 |
Draft CR to TS 38.141-2: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2203126 |
Draft CR to TS 36.104: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
R4-2203127 |
Draft CR to TS 36.141: RMR 900MHz and 1900MHz bands introduction |
Ericsson |
5.4.4 |
Others |
|
R4-2201688 |
TR_38.853_changes_clause 7.1 |
Union Inter. Chemins de Fer |
R4-2202246 |
TR_38.853_changes_clause 7.1 |
Union Inter. Chemins de Fer |
5.5.1 |
General |
|
R4-2201328 |
RMR 1900 MHz - TP to TR 38.852 on Regulatory background |
Ericsson |
R4-2201682 |
Revised TR 38.852 version 0.2.0 |
Union Inter. Chemins de Fer |
R4-2202242 |
Revised TR 38.852 version 0.2.0 |
Union Inter. Chemins de Fer |
5.5.3 |
BS RF requirements |
|
R4-2201329 |
RMR 1900 MHz - BS RF |
Ericsson |
R4-2201686 |
TR_38.852_changes_clause 9 |
Union Inter. Chemins de Fer |
R4-2201812 |
Cross-check on the implementation of ECC Decision (20)02 for RMR1900 |
Huawei |
R4-2201813 |
Remaining aspects for BS RF requirements for RMR1900 |
Huawei |
R4-2201814 |
TP to TR 38.852: BS RF requirements |
Huawei |
R4-2201815 |
Consideration of coordinated/un-coordinated deployments for the RMR1900 requirements in RAN4 specifications |
Huawei |
R4-2201997 |
draft CR to 37.104 on introduction of n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2202000 |
draft CR to 37.141 on introduction of n101 co-existence requirements |
Nokia, Nokia Shanghai Bell |
R4-2202004 |
draft CR to 38.104 on introduction of n101 (system parameters) |
Nokia, Nokia Shanghai Bell |
R4-2203052 |
TR_38.852_changes_clause 9 |
Union Inter. Chemins de Fer |
R4-2203058 |
TP to TR 38.852: BS RF requirements |
Huawei |
5.5.4 |
Others |
|
R4-2201683 |
TR_38.852_changes_clause 7.1 |
Union Inter. Chemins de Fer |
R4-2201685 |
TR_38.852_changes_clause 7.2 |
Union Inter. Chemins de Fer |
R4-2202243 |
TR_38.852_changes_clause 7.1 |
Union Inter. Chemins de Fer |
R4-2202244 |
TR_38.852_changes_clause 7.2 |
Union Inter. Chemins de Fer |
5.6 |
Issues arising from basket WIs but not subject to block approval |
|
R4-2202205 |
Email discussion summary for [101-bis-e][105] NR_Baskets_Part_1 |
Moderator (Skyworks Solutions) |
R4-2202305 |
Email discussion summary for [101-bis-e][105] NR_Baskets_Part_1 |
Moderator (Skyworks Solutions) |
5.6.1 |
UE RF requirements |
|
R4-2200059 |
TP to TR 38.717.02-01 for CA_n46-n48--n96 |
Charter Communications, Inc |
R4-2200176 |
TP to TR TR38.717-03-01 for CA_n46-n48-n96 |
Charter Communications, Inc |
R4-2200698 |
Working procedures for updating release independence specification |
Nokia, Nokia Shanghai Bell |
R4-2200706 |
n29 MSD in CA_n29-n71 |
Nokia, Dish |
R4-2201440 |
Discussion on the working procedure for introducing release independent features |
CHTTL |
R4-2201565 |
TP for TR 38.717-02-01 to include CA_n20-n67 |
Ericsson, BT plc |
R4-2201804 |
Discussion on the Rel-17 specifications: 25-series and 34-series |
Huawei |
R4-2202022 |
NR-U Contiguous UL-CA Measurements |
Skyworks Solutions Inc. |
R4-2202028 |
Corrections to Intra-band CA MSD for CA_n5B and CA_n7B |
Skyworks Solutions Inc. |
R4-2202034 |
Triple beat B3 MSD evaluation for DC_3A_n41C |
Skyworks Solutions Inc. |
R4-2202035 |
Measurements for CA_n29-n71 MSD |
Skyworks Solutions Inc. |
R4-2202036 |
Measurements for CA_n5-n28 MSD |
Skyworks Solutions Inc. |
R4-2202037 |
CA_n29A-n71A MSD |
Qualcomm Incorporated |
R4-2202038 |
MSD for DC_20A-38A_n8A |
Skyworks Solutions Inc. |
R4-2202039 |
Intra-band CA REFSENS Ambiguity |
Qualcomm Incorporated |
R4-2202154 |
Triple beat B3 MSD evaluation for DC_3A_n41C |
Skyworks Solutions Inc. |
R4-2202274 |
draftCR to R17 38-101-1 to correct intra-band CA REFSENS MSD test points |
Skyworks, Qualcomm |
R4-2202275 |
WF on LB-LB MSD |
Skyworks, Qualcomm |
R4-2202276 |
draftCR to R17 38-101-1 on MSD for CA_n29-n71 |
Dish, Nokia, Qualcomm, Skyworks |
R4-2202277 |
draftCR to R17 38-101-1 on MSD for CA_n5-n28 |
Skyworks |
R4-2202278 |
draftCR to R17 38-101-3 on MSD for DC_20A-38A_n8A |
Skyworks |
R4-2202279 |
WF on triple beat evaluation and specification framework |
Qualcomm, Skyworks |
R4-2202280 |
TP to TR for DC_2_n25 with 1UL |
Ericsson, Bell Mobility |
R4-2202281 |
TP to TR for CA_n46-n96 |
Charter Communications, Inc |
R4-2202282 |
TP to TR TR38.717-03-01 for CA_n46-n48-n96 |
Charter Communications, Inc |
R4-2202283 |
TP to TR 38.717.02-01 for CA_n46-n48--n96 |
Charter Communications, Inc |
R4-2202405 |
WF on introducing release independent features for TS 36.307 and TS 38.307 |
CHTTL, Nokia |
5.6.2 |
NR-U intra-band contiguous UL CA |
|
R4-2200851 |
On the MPR and A-MPR for intra-band UL CA with shared spectrum access |
Ericsson |
5.7.1 |
UE RF requirements for FR1 |
|
R4-2201104 |
TP to TR 38.717-01-01 Addition of CA_n40B |
Nokia, NBN |
R4-2202174 |
(TP to TR 38.717-01-01 Addition of CA_n40B |
Nokia, NBN |
5.8 |
NR inter-band Carrier Aggregation/Dual Connectivity for 2 bands DL with x bands UL (x=1, 2) |
|
R4-2201796 |
TR 38.717-02-01 v0.8.0 |
ZTE Wistron Telecom AB |
5.8.1 |
NR inter band CA requirements without any FR2 band(s) |
|
R4-2200060 |
TP to TR 38.717.02-01 for CA_n48-n96 |
Charter Communications, Inc |
R4-2200061 |
TP to TR 38.717.02-01 for CA_n46-n48 |
Charter Communications, Inc |
R4-2200193 |
Draft CR for 38.101-1: support of DC_n1A-n28A and DC_n1A-n41A |
SoftBank Corp. |
R4-2200201 |
Draft CR for TS 38.101-1: Support of BCS2 in CA_n41-n79 |
SoftBank Corp. |
R4-2201022 |
Draft CR for 38.101-1 to introduce CA_n1A-n77(3A) and CA_n18A-n77(3A) |
Samsung, KDDI |
R4-2201062 |
Draft CR for 38.101-1 to introduce new configurations of CA_n25-n77 |
Samsung, Telus, Bell Mobility |
R4-2201088 |
draftCR to add DC_n1A-n7A to 38.101-1 |
Nokia, BT |
R4-2201090 |
draftCR to add DC_n7A-n46 to 38.101-1 |
Nokia, BT |
R4-2201094 |
TP to TR 38.717-02-01 Addition of BCS1 for CA_n25-n77 |
Nokia, Telus |
R4-2201100 |
TP to TR 38.717-02-01 Addition of CA_n40-n77 |
Nokia, NBN |
R4-2201101 |
draftCR to add DC_n40B-n78 to 38.101-1 |
Nokia, NBN |
R4-2201105 |
draftCR 38.101-1 Addition of CA_n12A-n66(2A)(3A) |
Nokia, AT&T |
R4-2201106 |
draftCR 38.101-1 Addition of CA_n2(2A)-n12 |
Nokia, AT&T |
R4-2201107 |
draftCR 38.101-1 Addition of CA_n29A-n66(3A) |
Nokia, AT&T |
R4-2201546 |
draft CR 38.101-1 to add new configurations for CA_n25-n77 and CA_n41-n48 |
Eridsson, T-Mobile US |
R4-2201554 |
TP for TR 38.717-02-01 to include CA_n41-n70 |
Ericsson |
R4-2201555 |
TP for TR 38.717-02-01 to include CA_n70-n78 |
Ericsson |
R4-2201556 |
draft CR 38.101-1 to add new configurations for CA_n3-n79 |
Ericsson |
R4-2201559 |
TP for TR 38.717-02-01 to include dual UL for CA_n3-n20 |
Ericsson, BT plc |
R4-2201561 |
TP for TR 38.717-02-01 to include CA_n1-n67 |
Ericsson, BT plc |
R4-2201562 |
TP for TR 38.717-02-01 to include CA_n3-n67 |
Ericsson, BT plc |
R4-2201564 |
TP for TR 38.717-02-01 to include dual UL for CA_n1-n20 |
Ericsson, BT plc |
R4-2201681 |
Draft CR on CA_n1A-n8A |
China Unicom |
R4-2202175 |
TP to TR 38.717.02-01 for CA_n48-n96 |
Charter Communications, Inc |
R4-2202176 |
TP to TR 38.717.02-01 for CA_n46-n48 |
Charter Communications, Inc |
R4-2202177 |
Draft CR for TS 38.101-1: Support of BCS2 in CA_n41-n79 |
SoftBank Corp. |
R4-2202178 |
TP to TR 38.717-02-01 Addition of CA_n40-n77 |
Nokia, NBN |
R4-2202179 |
draftCR to add DC_n40B-n78 to 38.101-1 |
Nokia, NBN |
R4-2202180 |
TP for TR 38.717-02-01 to include CA_n41-n70 |
Ericsson |
R4-2202181 |
TP for TR 38.717-02-01 to include CA_n70-n78 |
Ericsson |
R4-2202182 |
TP for TR 38.717-02-01 to include dual UL for CA_n1-n20 |
Ericsson, BT plc |
5.8.2 |
NR inter band CA requirements with at least one FR2 band |
|
R4-2200192 |
Draft CR 38.101-3: support of DC_n1A-n257D |
SoftBank Corp. |
R4-2200621 |
Draft CR for TS 38.101-3 on corrections to CA configurations of CA_n25-n260 |
ZTE Corporation |
R4-2201023 |
Draft CR for 38.101-3 to introduce new configuratuons of DC_n77-n257 |
Samsung, KDDI |
R4-2201102 |
draftCR to add CA_n40-n257 to 38.101-1 |
Nokia, NBN |
R4-2201348 |
Draft CR for TS 38.101-3 on corrections to CA configurations of CA_n77(3A)-n257A |
ZTE Corporation |
R4-2202183 |
draftCR to add CA_n40-n257 to 38.101-1 |
Nokia, NBN |
5.9.1 |
UE RF requirements |
|
R4-2200189 |
Draft CR for 38.101-3: support of n77(3A) in 1UL CA_n3A/n28A-n77-n257A/D/G/H/I |
SoftBank Corp. |
R4-2200200 |
Draft CR for TS 38.101-1: Addition of missing CA_n3-n28-n41 Tib values |
SoftBank Corp. |
R4-2200606 |
Draft CR for TS 38.101-1: Adding same note for higher order combo of CA_n20-n28 |
MediaTek Inc. |
R4-2200607 |
Draft CR for TS 38.101-3: UL configuration correction of 48_n77's higher order combinations |
MediaTek Inc. |
R4-2200711 |
TP to TR 38.717-03-01: CA_n41-n66-n260 |
Nokia, TMO USA |
R4-2200712 |
TP to TR 38.717-03-01: CA_n66-n77-n260 |
Nokia, TMO USA |
R4-2201024 |
TP for TR 38.717-03-01 CA_n1-n3-n18 |
Samsung, KDDI |
R4-2201025 |
TP for TR 38.717-03-01 CA_n1-n18-n28 |
Samsung, KDDI |
R4-2201026 |
TP for TR 38.717-03-01 CA_n1-n18-n41 |
Samsung, KDDI |
R4-2201027 |
TP for TR 38.717-03-01 CA_n1-n18-n77 |
Samsung, KDDI |
R4-2201028 |
TP for TR 38.717-03-01 CA_n1-n28-n41 |
Samsung, KDDI |
R4-2201029 |
TP for TR 38.717-03-01 CA_n1-n28-n77 |
Samsung, KDDI |
R4-2201030 |
TP for TR 38.717-03-01 CA_n1-n41-n77 |
Samsung, KDDI |
R4-2201031 |
TP for TR 38.717-03-01 CA_n3-n18-n28 |
Samsung, KDDI |
R4-2201032 |
TP for TR 38.717-03-01 CA_n3-n18-n77 |
Samsung, KDDI |
R4-2201033 |
TP for TR 38.717-03-01 CA_n18-n28-n41 |
Samsung, KDDI |
R4-2201034 |
TP for TR 38.717-03-01 CA_n18-n28-n77 |
Samsung, KDDI |
R4-2201035 |
TP for TR 38.717-03-01 CA_n18-n41-n77 |
Samsung, KDDI |
R4-2201052 |
Draft CR for 38.101-1 to introduce new configurations to CA_n5-n48-n77 and CA_n48-n66-n77 with 1UL |
Samsung, Verizon |
R4-2201063 |
Draft CR for 38.101-1 to introduce new configurations to CA_n5-n25-n77 and CA_n5-n66-n77 with 1UL |
Samsung, Telus, Bell Mobility |
R4-2201108 |
TP to TR 38.717-03-01 Addition of CA_n12-n30-n66 |
Nokia, AT&T |
R4-2201109 |
TP to TR 38.717-03-01 Addition of CA_n29-n30-n66 |
Nokia, AT&T |
R4-2201110 |
TP to TR 38.717-03-01 Addition of CA_n2-n12-n30 |
Nokia, AT&T |
R4-2201111 |
TP to TR 38.717-03-01 Addition of CA_n2-n12-n66 |
Nokia, AT&T |
R4-2201112 |
TP to TR 38.717-03-01 Addition of CA_n2-n29-n30 |
Nokia, AT&T |
R4-2201113 |
TP to TR 38.717-03-01 Addition of CA_n2-n29-n66 |
Nokia, AT&T |
R4-2201552 |
TP for TR 38.717-03-01 to include CA_n41-n70-n78 |
Ericsson |
R4-2201566 |
TP for TR 38.717-03-01 to include CA_n1-n20-n67 |
Ericsson, BT plc |
R4-2201568 |
TP for TR 38.717-03-01 to include CA_n3-n20-n67 |
Ericsson, BT plc |
R4-2201724 |
TP for TR 38.717-03-01 to include CA_n2-n71-n78 |
Ericsson, Rogers |
R4-2201725 |
TP for TR 38.717-03-01 to include CA_n2-n66-n78 |
Ericsson, Rogers |
R4-2202184 |
Draft CR for TS 38.101-1: Adding same note for higher order combo of CA_n20-n28 |
MediaTek Inc. |
R4-2202185 |
Draft CR for 38.101-1 to introduce new configurations to CA_n5-n48-n77 and CA_n48-n66-n77 with 1UL |
Samsung, Verizon |
5.10 |
NR Inter-band Carrier Aggregation for 4 bands DL with 1 band UL |
|
R4-2202207 |
Email discussion summary for [101-bis-e][107] NR_Baskets_Part_3 |
Moderator (Nokia) |
5.10.1 |
UE RF requirements |
|
R4-2200211 |
TP for TR 38.717-04-01: CA_n1-n3-n28-n77 |
SoftBank Corp. |
R4-2200212 |
TP for TR 38.717-04-01: CA_n1-n3-n28-n79 |
SoftBank Corp. |
R4-2200213 |
TP for TR 38.717-04-01: CA_n1-n3-n28-n257 |
SoftBank Corp. |
R4-2200214 |
TP for TR 38.717-04-01: CA_n1-n3-n77-n79 |
SoftBank Corp. |
R4-2200215 |
TP for TR 38.717-04-01: CA_n1-n3-n79-n257 |
SoftBank Corp. |
R4-2200216 |
TP for TR 38.717-04-01: CA_n1-n28-n77-n79 |
SoftBank Corp. |
R4-2200217 |
TP for TR 38.717-04-01: CA_n1-n28-n77-n257 |
SoftBank Corp. |
R4-2200218 |
TP for TR 38.717-04-01: CA_n1-n28-n79-n257 |
SoftBank Corp. |
R4-2200219 |
TP for TR 38.717-04-01: CA_n3-n28-n41-n257 |
SoftBank Corp. |
R4-2200220 |
TP for TR 38.717-04-01: CA_n3-n41-n77-n257 |
SoftBank Corp. |
R4-2200221 |
TP for TR 38.717-04-01: CA_n28-n41-n77-n257 |
SoftBank Corp. |
R4-2200356 |
TP for CA_n28-n77-n79-n257 for TR 38.717-04-01 |
NTT DOCOMO, INC. |
R4-2200357 |
TP for CA_n28-n78-n79-n257 for TR 38.717-04-01 |
NTT DOCOMO, INC. |
R4-2200724 |
draft CR to add NR Inter-band CA for 4 bands in TS 38.101-1 |
Nokia, Verizon |
R4-2201065 |
TP for TR 38.717-04-01 CA_n5-n25-n66-n77 |
Samsung, Telus, Bell Mobility |
R4-2201120 |
TP to TR 38.717-04-01 Addition of CA_n2-n12-n30-n66 |
Nokia, AT&T |
R4-2201121 |
TP to TR 38.717-04-01 Addition of CA_n2-n29-n30-n66 |
Nokia, AT&T |
R4-2201550 |
TP for TR 38.717-04-01 to include CA_n41-n66-n70-n78 |
Ericsson |
R4-2201726 |
TP for TR 38.717-04-01 to include CA_n25-n41-n71-n78 |
Ericsson, Rogers |
R4-2201727 |
TP for TR 38.717-04-01 to include CA_n2-n66-n71-n78 |
Ericsson, Rogers |
R4-2201891 |
TP for TR 38.717-04-01 to include CA_n2A-n5A-n30A-n77A |
Ericsson, AT&T |
R4-2201892 |
TP for TR 38.717-04-01 to include CA_n2A-n5A-n66A-n77A |
Ericsson, AT&T |
R4-2201893 |
TP for TR 38.717-04-01 to include CA_n2A-n14A-n30A-n77A |
Ericsson, AT&T |
R4-2201894 |
TP for TR 38.717-04-01 to include CA_n2A-n14A-n66A-n77A |
Ericsson, AT&T |
R4-2201895 |
TP for TR 38.717-04-01 to include CA_n5A-n30A-n66-n77A |
Ericsson, AT&T |
R4-2201896 |
TP for TR 38.717-04-01 to include CA_n14A-n30A-n66A-n77A |
Ericsson, AT&T |
R4-2202186 |
TP for TR 38.717-04-01 to include CA_n2A-n5A-n66A-n77A |
Ericsson, AT&T |
5.11 |
NR Inter-band Carrier Aggregation/Dual connectivity for 3 bands DL with 2 bands UL |
|
R4-2201797 |
TR 38.717-03-02 v0.8.0 |
ZTE Wistron Telecom AB |
5.11.1 |
UE RF requirements |
|
R4-2200190 |
Draft CR for 38.101-1: support of n77(2A) in 2UL CA_n1A-n77-n79A |
SoftBank Corp. |
R4-2200191 |
Draft CR for 38.101-1: support of 2UL in CA_n3A-n28A-n77(3A) |
SoftBank Corp. |
R4-2200194 |
Draft CR for 38.101-1: support of 3 Bands DC_n1A-n3A-n77A and DC_n1A-n3A-n79A |
SoftBank Corp. |
R4-2200195 |
Draft CR for 38.101-1: support of 3 Bands DC_n1A-n77A-n79A, DC_n3A-n77A-n79A and DC_n3A-n77(2A)-n79A |
SoftBank Corp. |
R4-2200196 |
Draft CR for 38.101-1: support of 3 Bands DC_n3A-n28A-n41A, DC_n3A-n41A-n77A and DC_n28A-n41A-n77A |
SoftBank Corp. |
R4-2200202 |
TP for TR 38.717-03-02: CA_n1-n3-n79 |
SoftBank Corp. |
R4-2200203 |
TP for TR 38.717-03-02: CA_n1-n3-n257 |
SoftBank Corp. |
R4-2200204 |
TP for TR 38.717-03-02: CA_n1-n28-n41 |
SoftBank Corp. |
R4-2200205 |
TP for TR 38.717-03-02: CA_n1-n28-n77 |
SoftBank Corp. |
R4-2200206 |
TP for TR 38.717-03-02: CA_n1-n28-n79 |
SoftBank Corp. |
R4-2200207 |
TP for TR 38.717-03-02: CA_n1-n28-n257 |
SoftBank Corp. |
R4-2200208 |
TP for TR 38.717-03-02: CA_n1-n41-n77 |
SoftBank Corp. |
R4-2200209 |
TP for TR 38.717-03-02: CA_n1-n41-n257 |
SoftBank Corp. |
R4-2200210 |
TP for TR 38.717-03-02: CA_n41-n77-n257 |
SoftBank Corp. |
R4-2200351 |
BCS corrections for CA_n7-n66-n77 and CA_n66-n71-n77 |
Nokia, Nokia Shanghai Bell |
R4-2200355 |
TP for CA_n28-n78-n79 for TR 38.717-03-02 |
NTT DOCOMO, INC. MediaTek Inc. |
R4-2201036 |
TP for TR 38.717-03-02 CA_n1A-n3A-n18A |
Samsung, KDDI |
R4-2201037 |
TP for TR 38.717-03-02 CA_n1A-n18A-n28A |
Samsung, KDDI |
R4-2201038 |
TP for TR 38.717-03-02 CA_n1A-n18A-n41A |
Samsung, KDDI |
R4-2201039 |
TP for TR 38.717-03-02 CA_n1A-n18A-n77A |
Samsung, KDDI |
R4-2201040 |
TP for TR 38.717-03-02 CA_n1A-n28A-n41A |
Samsung, KDDI |
R4-2201041 |
TP for TR 38.717-03-02 CA_n1A-n28A-n77A |
Samsung, KDDI |
R4-2201042 |
TP for TR 38.717-03-02 CA_n1A-n41A-n77A |
Samsung, KDDI |
R4-2201043 |
TP for TR 38.717-03-02 CA_n3A-n18A-n28A |
Samsung, KDDI |
R4-2201044 |
TP for TR 38.717-03-02 CA_n3A-n18A-n77A |
Samsung, KDDI |
R4-2201045 |
TP for TR 38.717-03-02 CA_n18A-n28A-n41A |
Samsung, KDDI |
R4-2201046 |
TP for TR 38.717-03-02 CA_n18A-n28A-n77A |
Samsung, KDDI |
R4-2201047 |
TP for TR 38.717-03-02 CA_n18A-n41A-n77A |
Samsung, KDDI |
R4-2201048 |
Draft CR for 38.101-1 to introduce CA_n3A-n28A-n77(3A) and CA_n1A-n3A-n77(2A) |
Samsung, KDDI |
R4-2201049 |
Draft CR for 38.101-3 to introduce new combination for NR inter-band CA DC 3 bands DL with 2 bands UL |
Samsung, KDDI |
R4-2201053 |
TP for TR 38.717-03-02 CA_n2-n5-n48 |
Samsung, Verizon |
R4-2201054 |
TP for TR 38.717-03-02 CA_n2-n48-n66 |
Samsung, Verizon |
R4-2201055 |
TP for TR 38.717-03-02 CA_n2-n48-n77 |
Samsung, Verizon |
R4-2201056 |
TP for TR 38.717-03-02 CA_n5-n48-n66 |
Samsung, Verizon |
R4-2201057 |
TP for TR 38.717-03-02 CA_n5-n48-n77 |
Samsung, Verizon |
R4-2201058 |
TP for TR 38.717-03-02 CA_n48-n66-n77 |
Samsung, Verizon |
R4-2201064 |
Draft CR for 38.101-1 to introduce new configurations to CA_n5-n25-n77 and CA_n5-n66-n77 with 2UL |
Samsung, Telus, Bell Mobility |
R4-2201086 |
TP to TR 38.717-03-02 Addition of CADC_n7A-n46-n78A |
Nokia, BT |
R4-2201087 |
draftCR to add n78(2A) to CA_n7A-n28A-n78 already in 38.101-1 |
Nokia, BT |
R4-2201103 |
draftCR to add CA_n40-n78-n257 to 38.101-1 |
Nokia, NBN |
R4-2201114 |
TP to TR 38.717-03-02 Addition of CA_n12-n30-n66 |
Nokia, AT&T |
R4-2201115 |
TP to TR 38.717-03-02 Addition of CA_n29-n30-n66 |
Nokia, AT&T |
R4-2201116 |
TP to TR 38.717-03-02 Addition of CA_n2-n12-n30 |
Nokia, AT&T |
R4-2201117 |
TP to TR 38.717-03-02 Addition of CA_n2-n12-n66 |
Nokia, AT&T |
R4-2201118 |
TP to TR 38.717-03-02 Addition of CA_n2-n29-n30 |
Nokia, AT&T |
R4-2201119 |
TP to TR 38.717-03-02 Addition of CA_n2-n29-n66 |
Nokia, AT&T |
R4-2201349 |
Draft CR for TS 38.101-3 Add a note for BCS in 3DL NR CA table |
ZTE Corporation |
R4-2201516 |
DraftCR for 38.101-1: Correction on CA_n7-n66-n78 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2201517 |
DraftCR for 38.101-1: CA_n25(2A)-n38A-n66(2A) |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2201518 |
DraftCR for 38.101-1: additional combinations for CA_n7-n25-n66 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2201547 |
draft CR 38.101-1 to add new configurations for CA_n25-n41-n66, CA_n25-n41-n71, CA_n25-n66-n71, CA_n41-n66-n71, CA_n66-n71-n77 |
Eridsson, T-Mobile US |
R4-2201548 |
TP for TR 38.717-03-02 to include CA_n41-n66-n260 |
Eridsson, T-Mobile US |
R4-2201549 |
TP for TR 38.717-03-02 to include DC_n41-n66-n260 |
Eridsson, T-Mobile US |
R4-2201553 |
TP for TR 38.717-03-02 to include CA_n41-n70-n78 |
Ericsson |
R4-2201560 |
TP for TR 38.717-03-02 to include CA_n1-n3-n20 |
Ericsson, BT plc |
R4-2201563 |
TP for TR 38.717-03-02 to include CA_n1-n3-n67 |
Ericsson, BT plc |
R4-2201567 |
TP for TR 38.717-03-02 to include CA_n1-n20-n67 |
Ericsson, BT plc |
R4-2201569 |
TP for TR 38.717-03-02 to include CA_n3-n20-n67 |
Ericsson, BT plc |
R4-2201578 |
draft CR 38.101-3 to add new 3DL CA combinations with FR2 |
Ericsson, Telstra |
R4-2201579 |
draft CR 38.101-3 to add new 3DL DC combinations with FR2 |
Ericsson, Telstra |
R4-2202187 |
TP to TR 38.717-03-02 Addition of CADC_n7A-n46-n78A |
Nokia, BT |
R4-2202188 |
TP to TR 38.717-03-02 Addition of CA_n29-n30-n66 |
Nokia, AT&T |
R4-2202189 |
TP for TR 38.717-03-02 to include CA_n41-n66-n260 |
Eridsson, T-Mobile US |
R4-2202190 |
TP for TR 38.717-03-02 to include CA_n41-n70-n78 |
Ericsson |
5.12.1 |
UE RF requirements |
|
R4-2200197 |
Draft CR for 38.101-3: support of 4 Bands DC_n28A-n77A-n79A-257A/G/H/I and DC_n28A-n77(2A)-n79A-257A/G/H/I |
SoftBank Corp. |
R4-2200198 |
Draft CR for 38.101-3: additions of Low+Low UL configurations for 4 Bands DC_n3A-n28A-n77A-257A/G/H/I and DC_n3A-n28A-n77(2A)-257A/G/H/I |
SoftBank Corp. |
R4-2200199 |
Draft CR for 38.101-3: support of 4 Bands DC_n3A-n28A-n79A-257A/G/H/I |
SoftBank Corp. |
R4-2200358 |
TP for CA_n28-n78-n79-n257 for TR 38.717-04-02 |
NTT DOCOMO, INC. |
R4-2200359 |
Draft CR for TS 38.101-3: DC_n28-n77-n79-n257 and DC_n28-n78-n79-n257 |
NTT DOCOMO, INC. |
R4-2201050 |
Draft CR for 38.101-3 to introduce new combinations for NR inter-band CA DC 4 bands DL with 2 bands UL |
Samsung, KDDI |
R4-2201066 |
TP for TR 38.717-04-02 CA_n5-n25-n66-n77 |
Samsung, Telus, Bell Mobility |
R4-2201122 |
TP to TR 38.717-04-02 Addition of CA_n2-n12-n30-n66 |
Nokia, AT&T |
R4-2201123 |
TP to TR 38.717-04-02 Addition of CA_n2-n29-n30-n66 |
Nokia, AT&T |
R4-2201551 |
TP for TR 38.717-04-02 to include CA_n41-n66-n70-n78 |
Ericsson |
R4-2201580 |
draft CR 38.101-3 to add new 4DL CA combinations with FR2 |
Ericsson, Telstra |
R4-2201581 |
draft CR 38.101-3 to add new 4DL DC combinations with FR2 |
Ericsson, Telstra |
R4-2201897 |
TP for TR 38.717-04-02 to include CA_n2A-n5A-n30A-n77A |
Ericsson, AT&T |
R4-2201898 |
TP for TR 38.717-04-02 to include CA_n2A-n5A-n66A-n77A |
Ericsson, AT&T |
R4-2201899 |
TP for TR 38.717-04-02 to include CA_n2A-n14A-n30A-n77A |
Ericsson, AT&T |
R4-2201900 |
TP for TR 38.717-04-02 to include CA_n14A-n30A-n66A-n77A |
Ericsson, AT&T |
R4-2201901 |
TP for TR 38.717-04-02 to include CA_n2A-n14A-n66A-n77A |
Ericsson, AT&T |
R4-2201902 |
TP for TR 38.717-04-02 to include CA_n5A-n30A-n66-n77A |
Ericsson, AT&T |
R4-2202191 |
Draft CR for TS 38.101-3: DC_n28-n77-n79-n257 and DC_n28-n78-n79-n257 |
NTT DOCOMO, INC. |
R4-2202192 |
TP for TR 38.717-04-02 to include CA_n2A-n5A-n66A-n77A |
Ericsson, AT&T |
5.13.1 |
UE RF requirements |
|
R4-2200222 |
TP for TR 38.717-05-01: CA_n3-28-n77-n79-n257 |
SoftBank Corp. |
5.14 |
DC of 1 LTE band and 1 NR band |
|
R4-2201362 |
TR 37.717-11-11 v1.1.0 Rel-17 Dual Connectivity (DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) |
CHTTL |
R4-2202206 |
Email discussion summary for [101-bis-e][106] NR_Baskets_Part_2 |
Moderator (Nokia) |
5.14.1 |
EN-DC requirements without FR2 band |
|
R4-2200185 |
Draft CR for 38.101-3: corrections of MOP in DC_42C_n1A |
SoftBank Corp. |
R4-2200237 |
TP update for TR 37.717-11-11: DC_11_n1 |
SoftBank Corp. |
R4-2200827 |
TP for TR 37.717-11-11: DC_n28A_8C |
CMCC |
R4-2200828 |
TP for TR 37.717-11-11: DC_n41_39 |
CMCC |
R4-2200829 |
TP for TR 37.717_11_11 DC_n41_3 |
CMCC |
R4-2200830 |
TP for TR 37.717_11_11 DC_n41_8 |
CMCC |
R4-2200831 |
TP for TR 37.717_11_11 DC_n41_40 |
CMCC |
R4-2201051 |
TP for TR 37.717-11-11 DC_5_n3 |
Samsung, Reliance Jio |
R4-2201091 |
draftCR to add DC_3C_n20A to 38.101-3 |
Nokia, BT |
R4-2201557 |
TP for TR 37.717-11-11 to include DC_5_n1 |
Ericsson, Airtel |
R4-2201558 |
TP for TR 37.717-11-11 to include DC_5_n3 |
Ericsson, Airtel |
R4-2201728 |
draft CR 38.101-3 to add new configurations for DC_2_n78 and DC_71_n78 |
Ericsson, Rogers |
R4-2202153 |
TP for TR 37.717-11-11 to include DC_5_n3 |
Ericsson, Airtel |
R4-2202157 |
TP for TR 37.717-11-11: DC_n28A_8C |
CMCC |
R4-2202158 |
TP for TR 37.717-11-11: DC_n41_39 |
CMCC |
R4-2202159 |
TP for TR 37.717_11_11 DC_n41_3 |
CMCC |
R4-2202160 |
TP for TR 37.717_11_11 DC_n41_8 |
CMCC |
R4-2202161 |
TP for TR 37.717_11_11 DC_n41_40 |
CMCC |
R4-2202162 |
draftCR to add DC_3C_n20A to 38.101-3 |
Nokia, BT |
R4-2202163 |
TP for TR 37.717-11-11 to include DC_5_n1 |
Ericsson, Airtel |
R4-2202164 |
draft CR 38.101-3 to add new configurations for DC_2_n78 and DC_71_n78 |
Ericsson, Rogers |
5.15 |
DC of 2 LTE band and 1 NR band |
|
R4-2200367 |
TP for TR 37.717-21-11 DC_n3A_1A-8A |
Huawei Technologies France |
R4-2200368 |
TP for TR 37.717-21-11: DC_n77A_1A-8A and DC_n77(2A)_1A-8A |
Huawei Technologies France |
R4-2200369 |
TP for TR 37.717-21-11 DC_n77A_3A_1A |
Huawei Technologies France |
R4-2200370 |
TP for TR 37.717-21-11 DC_n77A_3A-8A and DC_n77(2A)_3A-8A |
Huawei Technologies France |
R4-2200371 |
TP for TR 37.717-21-11: DC_n257A_3A-1A |
Huawei Technologies France |
R4-2200372 |
TP for TR 37.717-21-11 DC_n257A_3A-8A |
Huawei Technologies France |
5.15.1 |
EN-DC requirements without FR2 band |
|
R4-2200186 |
Draft CR for 38.101-3: support of n77(3A) in 2LTE+1NR DC_1A/3A/8A/11A_n77 |
SoftBank Corp. |
R4-2200235 |
TP for TR 37.717-21-11: EN-DC_8-41_n1 |
SoftBank Corp., LG Electronics |
R4-2200375 |
TP for TR 37.717-21-11: DC_1A_(n)3AA |
Huawei Technologies France |
R4-2200608 |
CR for TS 38.101-3: Adding same note for higher order combo of DC_20_n28 |
MediaTek Inc. |
R4-2201089 |
draftCR to add DC_n1A-n7A-n78A to 38.101-1 |
Nokia, BT |
R4-2201095 |
TP to TR 37.717-21-11 Addition of DC_2A-38A_n78A |
Nokia |
R4-2201096 |
TP to TR 37.717-21-11 Addition of DC_2A-28A_n78A |
Nokia |
R4-2201097 |
draftCR to add DC_2-7_n28 and DC_5-66_n78 to 38.101-3 |
Nokia |
R4-2201356 |
TP for TR 37.717-21-11_DC_1A-38A_n78A |
ZTE Corporation |
R4-2201357 |
TP for TR 37.717-21-11_DC_7A-38A_n78A |
ZTE Corporation |
R4-2201573 |
TP for TR 37.717-21-11 to include DC_2-7_n25 |
Ericsson, Bell Mobility |
R4-2201729 |
draft CR 38.101-3 to add new configurations for DC_12-66_n78, DC_2-71_n78, DC_7-12_n78, DC_7-71_n78, DC_66-71_n78 |
Ericsson, Rogers |
R4-2202005 |
TP update for TR 37.717-21-11: EN-DC_1-11_n79 |
SoftBank Corp., LG Electronics |
R4-2202007 |
TP update for TR 37.717-21-11: EN-DC_8-11_n79 |
SoftBank Corp., LG Electronics |
R4-2202165 |
Draft CR for 38.101-3: support of n77(3A) in 2LTE+1NR DC_1A/3A/8A/11A_n77 |
SoftBank Corp. |
R4-2202166 |
TP for TR 37.717-21-11: EN-DC_8-41_n1 |
SoftBank Corp., LG Electronics |
R4-2202167 |
CR for TS 38.101-3: Adding same note for higher order combo of DC_20_n28 |
MediaTek Inc. |
R4-2202168 |
TP to TR 37.717-21-11 Addition of DC_2A-38A_n78A |
Nokia |
R4-2202169 |
TP to TR 37.717-21-11 Addition of DC_2A-28A_n78A |
Nokia |
R4-2202170 |
draftCR to add DC_2-7_n28 and DC_5-66_n78 to 38.101-3 |
Nokia |
R4-2202171 |
draft CR 38.101-3 to add new configurations for DC_12-66_n78, DC_2-71_n78, DC_7-12_n78, DC_7-71_n78, DC_66-71_n78 |
Ericsson, Rogers |
5.16 |
DC of 3 LTE band and 1 NR band |
|
R4-2200373 |
TP for TR 37.717-31-11 DC_n77A_1A-3A-8A and DC_n77(2A)_1A-3A-8A |
Huawei Technologies France |
5.16.1 |
EN-DC requirements without FR2 band |
|
R4-2200609 |
CR for TS 38.101-3: Adding same note for higher order combo of DC_20_n28 |
MediaTek Inc. |
R4-2200623 |
Draft CR for TS 38.101-3 to add UL DC_20A_n78A support for DC_1A-20A-38A_n78A and DC_3A-20A-38A_n78A |
ZTE Corporation |
R4-2200624 |
TP for TR 37.717-31-11_DC_1A-3A-38A_n78A |
ZTE Corporation |
R4-2200713 |
TP to TR 37.717-31-11: DC_2-5-48_n77 |
Nokia, Verizon |
R4-2200714 |
TP to TR 37.717-31-11: DC_5-48-66_n77 |
Nokia, Verizon |
R4-2200715 |
TP to TR 37.717-31-11: DC_2-13-48_n77 |
Nokia, Verizon |
R4-2201059 |
Draft CR for 38.101-3 to introduce DC_7A-7A-29A-66A_n78A and DC_7C-29A-66A_n78A |
Samsung, Telus, Bell Mobility |
R4-2201060 |
TP for TR 37.717-31-11 DC_2-7-29_n78 |
Samsung, Telus, Bell Mobility |
R4-2201098 |
TP to TR 37.717-31-11 Addition of DC_2-7-28_n78 |
Nokia |
R4-2201099 |
TP to TR 37.717-31-11 Addition of DC_5-7-66_n78 |
Nokia |
R4-2201233 |
Draft CR for 38.101-3 To configuration DC_3C-7A-20A_n28A |
Huawei, HiSilicon |
R4-2201234 |
Draft CR for 38.101-3 To configuration DC_3C-20A-32A_n1A |
Huawei, HiSilicon |
R4-2201235 |
Draft CR for 38.101-3 To add UL configuration DC_3C_n78A for DC_3C-7A-20A_n78A |
Huawei, HiSilicon |
R4-2201236 |
Draft CR for 38.101-3 To add UL configuration DC_3C_n28A for DC_1A-3C-20A_n28A |
Huawei, HiSilicon |
R4-2201358 |
TP for TR 37.717-31-11_DC_1A-7A-38A_n78A |
ZTE Corporation |
R4-2201359 |
TP for TR 37.717-31-11_DC_7A-20A-38A_n78A |
ZTE Corporation |
R4-2201574 |
TP for TR 37.717-31-11 to include DC_2-7-66_n25 |
Ericsson, Bell Mobility |
R4-2201575 |
TP for TR 37.717-31-11 to include DC_2-7-13_n25 |
Ericsson, Bell Mobility |
R4-2201730 |
TP for TR 37.717-31-11 to include DC_2-5-7_n78 |
Ericsson, Rogers |
R4-2201731 |
TP for TR 37.717-31-11 to include DC_2-5-66_n78 |
Ericsson, Rogers |
R4-2201732 |
TP for TR 37.717-31-11 to include DC_5-7-66_n78 |
Ericsson, Rogers |
R4-2202172 |
TP to TR 37.717-31-11: DC_2-5-48_n77 |
Nokia, Verizon |
5.16.2 |
EN-DC requirements with FR2 band |
|
R4-2201903 |
draft CR 38101-3 to add DC_2A-2A-5A-66A_n260M and DC_2A-2A-5A-66A_n260M |
Ericsson, AT&T |
R4-2201904 |
draft CR 38101-3 to add DC_2A-2A-12A-30A_n260M |
Ericsson, AT&T |
R4-2201905 |
draft CR 38101-3 to add DC_2A-2A-12A-66A_n260M and DC_2A-12A-66A-66A_n260M |
Ericsson, AT&T |
R4-2201906 |
draft CR 38101-3 to add DC_5A-30A-66A-66A_n260M |
Ericsson, AT&T |
R4-2201907 |
draft CR 38101-3 to add DC_12A-30A-66A-66A_n260M |
Ericsson, AT&T |
R4-2201908 |
draft CR 38101-3 to add DC_12A-30A-66A-66A_n260M |
Ericsson, AT&T |
R4-2201961 |
draft CR 38101-3 to add DC_2A-2A-5A-30A_n260M |
Ericsson, AT&T |
5.17.1 |
EN-DC requirements without FR2 band |
|
R4-2200610 |
CR for TS 38.101-3: Adding same note for higher order combo of DC_20_n28 |
MediaTek Inc. |
R4-2200622 |
Draft CR for TS 38.101-3 to add UL DC_1A_n78A support for DC_1A-3A-20A-38A_n78A |
ZTE Corporation |
R4-2201061 |
TP for TR 37.717-41-11 DC_2-7-29-66_n78 |
Samsung, Telus, Bell Mobility |
R4-2201733 |
TP for TR 37.717-41-11 to include DC_2-5-7-66_n78 |
Ericsson, Rogers |
R4-2202173 |
TP for TR 37.717-41-11 to include DC_2-5-7-66_n78 |
Ericsson, Rogers |
5.17.2 |
EN-DC requirements with FR2 band |
|
R4-2201909 |
draft CR 38101-3 to add DC_2A-5A-30A-66A_n260M |
Ericsson, AT&T |
R4-2201910 |
draft CR 38101-3 to add DC_2A-12A-30A-66A_n260M |
Ericsson, AT&T |
5.19 |
DC of x bands (x=1,2, 3, 4) LTE inter-band CA and 2 bands NR inter-band CA |
|
R4-2200789 |
TR 37.717-11-21 v0.8.0 TR update: LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics France |
R4-2200791 |
Revised WID on LTE (xDL/UL x=1.2,3,4) with NR 2 bands (2DL/1UL) DC in Rel-17 |
LG Electronics France |
R4-2200792 |
Introduction CR on new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) band combinations in Rel-17 |
LG Electronics France |
5.19.1 |
EN-DC requirements including NR inter CA without FR2 band |
|
R4-2200225 |
TP for TR 37.717-11-21: EN-DC_1-8_n28-n79 |
SoftBank Corp. |
R4-2200226 |
TP for TR 37.717-11-21: EN-DC_1-8_n77-n79 |
SoftBank Corp. |
R4-2200227 |
TP for TR 37.717-11-21: EN-DC_3-8_n77-n79 |
SoftBank Corp. |
R4-2200228 |
TP for TR 37.717-11-21: EN-DC_8_n1-n3 |
SoftBank Corp. |
R4-2200231 |
TP for TR 37.717-11-21: EN-DC_8-41_n3-n77 |
SoftBank Corp. |
R4-2200232 |
TP for TR 37.717-11-21: EN-DC_8-42_n1-n77 |
SoftBank Corp. |
R4-2200233 |
TP for TR 37.717-11-21: EN-DC_41_n1-n77 |
SoftBank Corp. |
R4-2200234 |
TP for TR 37.717-11-21: EN-DC_42_n1-n3 |
SoftBank Corp. |
R4-2200236 |
TP for TR 37.717-11-21: EN-DC_11_n3-n79 |
SoftBank Corp. |
R4-2200716 |
TP to TR 37.717-11-21: DC_13-66_n5-n77 |
Nokia, Verizon |
R4-2200717 |
TP to TR 37.717-11-21: DC_2-66_n5-n77 |
Nokia, Verizon |
R4-2200718 |
TP to TR 37.717-11-21: DC_2-13_n66-n77 |
Nokia, Verizon |
R4-2200719 |
TP to TR 37.717-11-21: DC_2-66_n66-n77 |
Nokia, Verizon |
R4-2200720 |
TP to TR 37.717-11-21: DC_2-5-66_n66-n77 |
Nokia, Verizon |
R4-2200721 |
TP to TR 37.717-11-21: DC_2-2-13-66_n66-n77 |
Nokia, Verizon |
R4-2200722 |
TP to TR 38.717-05-01: CA_n2-n5-n48-n66-n77 |
Nokia, Verizon |
R4-2200723 |
TP to TR 38.717-04-02: CA_n2-n5-n66-n77 |
Nokia, Verizon |
R4-2200725 |
draftCR 38.101-3 introduction of 2LTE and 2NR bandcombinations |
Nokia, Verizon |
R4-2200794 |
MSD test results and test configurations for new NR DC band combinations |
LG Electronics France |
R4-2201092 |
draftCR to add DC_3_n1A-n78(2A) to 38.101-3 |
Nokia, BT |
R4-2201093 |
draftCR to add DC_3_n28A-n78(2A) to 38.101-3 |
Nokia, BT |
R4-2201237 |
TP for TR 37.717-11-21: DC_3A-32A_n1A-n28A and DC_3C-32A_n1A-n28A |
Huawei, HiSilicon |
R4-2201238 |
TP for TR 37.717-11-21: DC_20A-32A_n1A-n28A |
Huawei, HiSilicon |
R4-2201239 |
TP for TR 37.717-11-21: DC_3A-20A-32A_n1A-n28A and DC_3C-20A-32A_n1A-n28A |
Huawei, HiSilicon |
R4-2201240 |
TP for TR 37.717-11-21: DC_1A_n28A-n75A |
Huawei, HiSilicon |
R4-2201241 |
TP for TR 37.717-11-21: DC_3A_n28A-n75A and DC_3C_n28A-n75A |
Huawei, HiSilicon |
R4-2201242 |
TP for TR 37.717-11-21: DC_1A-3A_n28A-n75A and DC_1A-3C_n28A-n75A |
Huawei, HiSilicon |
R4-2201243 |
TP for TR 37.717-11-21: DC_3A-20A_n28A-n75A and DC_3C-20A_n28A-n75A |
Huawei, HiSilicon |
R4-2201244 |
TP for TR 37.717-11-21: DC_1A-20A_n28A-n75A |
Huawei, HiSilicon |
R4-2201245 |
TP for TR 37.717-11-21: DC_1A-3A-20A_n28A-n75A and DC_1A-3C-20A_n28A-n75A |
Huawei, HiSilicon |
R4-2201246 |
Draft CR for 38.101-3 to add UL configuration DC_3C_n1A and DC_3C_n78A for DC_3C-7C_n1A-n78A |
Huawei, HiSilicon |
R4-2201350 |
TP for TR 37.717-11-21: DC_1A_n3A-n78A |
ZTE Corporation |
R4-2201351 |
TP for TR 37.717-11-21_DC_1A-38A_n3A-n78A |
ZTE Corporation |
R4-2201352 |
TP for TR 37.717-11-21_DC_7A-38A_n3A-n78A |
ZTE Corporation |
R4-2201353 |
TP for TR 37.717-11-21_DC_20A_n3A-n78A |
ZTE Corporation |
R4-2201354 |
TP for TR 37.717-11-21_DC_20A-38A_n3A-n78A. |
ZTE Corporation |
R4-2201355 |
TP for TR 37.717-11-21_DC_38A_n3A-n78A |
ZTE Corporation |
R4-2201519 |
TP for TR 37.717-11-21: DC_2-7-66_n66-n77 |
Huawei, HiSilicon, Bell Mobility, Telus |
R4-2201570 |
TP for TR 37.717-11-21 to include DC_20_n1-n67 |
Ericsson, BT plc |
R4-2201571 |
TP for TR 37.717-11-21 to include DC_20_n3-n67 |
Ericsson, BT plc |
R4-2201572 |
TP for TR 37.717-11-21 to include DC_3_n20-n67 |
Ericsson, BT plc |
R4-2201576 |
TP for TR 37.717-11-21 to include DC_2_n25-n66 |
Ericsson, Bell Mobility |
R4-2201577 |
TP for TR 37.717-11-21 to include DC_2-66_n25-n66 |
Ericsson, Bell Mobility |
R4-2201734 |
draft CR 38.101-3 to add new configurations for DC_2_n66-n78 and DC_2_n71-n78 |
Ericsson, Rogers |
R4-2201735 |
TP for TR 37.717-11-21 to include DC_5_n2-n78 |
Ericsson, Rogers |
R4-2201736 |
TP for TR 37.717-11-21 to include DC_66_n2-n78 |
Ericsson, Rogers |
R4-2201737 |
TP for TR 37.717-11-21 to include DC_12_n2-n78 |
Ericsson, Rogers |
R4-2201738 |
TP for TR 37.717-11-21 to include DC_2-5_n66-n78 |
Ericsson, Rogers |
R4-2201739 |
TP for TR 37.717-11-21 to include DC_2-5_n2-n78 |
Ericsson, Rogers |
R4-2201740 |
TP for TR 37.717-11-21 to include DC_2-66_n2-n78 |
Ericsson, Rogers |
R4-2201741 |
TP for TR 37.717-11-21 to include DC_5-66_n2-n78 |
Ericsson, Rogers |
R4-2201742 |
TP for TR 37.717-11-21 to include DC_2-7_n2-n78 |
Ericsson, Rogers |
R4-2201743 |
TP for TR 37.717-11-21 to include DC_2-7_n71-n78 |
Ericsson, Rogers |
R4-2201744 |
TP for TR 37.717-11-21 to include DC_2-12_n2-n78 |
Ericsson, Rogers |
R4-2201745 |
TP for TR 37.717-11-21 to include DC_2-12_n66-n78 |
Ericsson, Rogers |
R4-2201746 |
TP for TR 37.717-11-21 to include DC_2-66_n71-n78 |
Ericsson, Rogers |
R4-2201747 |
TP for TR 37.717-11-21 to include DC_2-71_n2-n78 |
Ericsson, Rogers |
R4-2201748 |
TP for TR 37.717-11-21 to include DC_2-71_n66-n78 |
Ericsson, Rogers |
R4-2201749 |
TP for TR 37.717-11-21 to include DC_5-7_n2-n78 |
Ericsson, Rogers |
R4-2201750 |
TP for TR 37.717-11-21 to include DC_5-7_n66-n78 |
Ericsson, Rogers |
R4-2201751 |
TP for TR 37.717-11-21 to include DC_7-12_n2-n78 |
Ericsson, Rogers |
R4-2201752 |
TP for TR 37.717-11-21 to include DC_7-12_n66-n78 |
Ericsson, Rogers |
R4-2201753 |
TP for TR 37.717-11-21 to include DC_7-66_n2-n78 |
Ericsson, Rogers |
R4-2201754 |
TP for TR 37.717-11-21 to include DC_7-66_n71-n78 |
Ericsson, Rogers |
R4-2201755 |
TP for TR 37.717-11-21 to include DC_7-71_n2-n78 |
Ericsson, Rogers |
R4-2201756 |
TP for TR 37.717-11-21 to include DC_7-71_n66-n78 |
Ericsson, Rogers |
R4-2201757 |
TP for TR 37.717-11-21 to include DC_12-66_n2-n78 |
Ericsson, Rogers |
R4-2201758 |
TP for TR 37.717-11-21 to include DC_66-71_n2-n78 |
Ericsson, Rogers |
R4-2202193 |
TP for TR 37.717-11-21: DC_1A_n28A-n75A |
Huawei, HiSilicon |
R4-2202194 |
TP for TR 37.717-11-21: DC_3A_n28A-n75A and DC_3C_n28A-n75A |
Huawei, HiSilicon |
R4-2202195 |
TP for TR 37.717-11-21: DC_1A-3A_n28A-n75A and DC_1A-3C_n28A-n75A |
Huawei, HiSilicon |
R4-2202196 |
TP for TR 37.717-11-21: DC_3A-20A_n28A-n75A and DC_3C-20A_n28A-n75A |
Huawei, HiSilicon |
R4-2202197 |
TP for TR 37.717-11-21: DC_1A-20A_n28A-n75A |
Huawei, HiSilicon |
R4-2202198 |
TP for TR 37.717-11-21: DC_1A-3A-20A_n28A-n75A and DC_1A-3C-20A_n28A-n75A |
Huawei, HiSilicon |
R4-2202199 |
TP for TR 37.717-11-21_DC_38A_n3A-n78A |
ZTE Corporation |
R4-2202200 |
TP for TR 37.717-11-21 to include DC_3_n20-n67 |
Ericsson, BT plc |
R4-2202289 |
MPR study for PC1 FWA device |
Nokia, Nokia Shanghai Bell |
5.19.2 |
EN-DC requirements including NR inter CA with FR2 band |
|
R4-2200793 |
TP on summary of self-interference analysis for new NR DC LTE(xDL/1UL)+ NR(2DL/1UL) DC in Rel-17 |
LG Electronics France |
5.21.1 |
UE RF requirements |
|
R4-2200187 |
Draft CR for 38.101-3: the support of n77(2A) in DC_8A_n3A-n77-n79A |
SoftBank Corp. |
R4-2200224 |
TP for TR 37.716-11-31: EN-DC_1-8_n3-n77-n79 |
SoftBank Corp. |
R4-2200229 |
TP for TR 37.717-11-31: EN-DC_8_n3-n28-n79 |
SoftBank Corp. |
R4-2200230 |
TP for TR 37.717-11-31: EN-DC_8_n28-n77-n79 |
SoftBank Corp. |
R4-2201438 |
TP for TR 37.717-11-31: support of DC_3_n1-n8-n78, DC_3-3_n1-n8-n78, DC_7_n1-n8-n78, DC_7-7_n1-n8-n78 |
CHTTL |
R4-2201439 |
TP for TR 37.717-11-31: support of DC_3-7_n1-n8-n78, DC_3-3-7_n1-n8-n78, DC_3-7-7_n1-n8-n78, DC_3-3-7-7_n1-n8-n78 |
CHTTL |
5.23.1 |
UE RF requirements |
|
R4-2200223 |
TP for TR 37.717-11-41: EN-DC_1_n3-n28-n77-n79 |
SoftBank Corp. |
5.24.1 |
UE RF requirements |
|
R4-2200188 |
CR for TS 38.101-1: Applicability correction for SUL_n41-n97 |
MediaTek Inc. |
5.25 |
Band combinations for Uu and V2X con-current operation |
|
R4-2202208 |
Email discussion summary for [101-bis-e][108] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
R4-2202308 |
Email discussion summary for [101-bis-e][108] NR_LTE_V2X_PC5_combos |
Moderator (CATT) |
5.25.1 |
UE RF requirements |
|
R4-2200144 |
TR37.875, Band combinations of V2X con-current operation |
CATT |
R4-2200145 |
TP on coexistence study of V2X_n8A-n47A, V2X_8A_n47A and V2X_n8A_47A |
CATT |
R4-2200146 |
Draft CR for TS 38.101-1, Introduce new band combinations of V2X_n8A-n47A |
CATT |
R4-2200147 |
Draft CR for TS 38.101-3, Introduce new band combination of V2X_n8A_47A and V2X_8A_n47A |
CATT |
R4-2200508 |
Calculation of MSD for V2X_1A-n47A and V2X_n1A-47A and accompanying TP |
Qualcomm Incorporated |
R4-2202155 |
Calculation of MSD for V2X_1A-n47A and V2X_n1A-47A and accompanying TP |
Qualcomm Incorporated |
R4-2202284 |
TP on coexistence study of V2X_n8A-n47A, V2X_8A_n47A and V2X_n8A_47A |
CATT |
5.26 |
Adding channel bandwidth support to existing NR bands |
|
R4-2202209 |
Email discussion summary for [101-bis-e][109] NR_bands_R17_BWs |
Moderator (Ericsson) |
R4-2202309 |
Email discussion summary for [101-bis-e][109] NR_bands_R17_BWs |
Moderator (Ericsson) |
5.26.1 |
UE RF requirements |
|
R4-2200922 |
On new channel bandwidths narrower than 40 MHz of n79 |
Samsung |
R4-2200923 |
Draft LS on CORESET#0 impact of CBW narrower than 40MHz of n79 |
Samsung |
R4-2202285 |
WF on adding 100 MHz channel BW in NR-U bands n46 and n96. |
Qualcomm |
R4-2202286 |
LS on CORESET#0 impact of CBW narrower than 40MHz of n79 |
Samsung |
5.26.1.1 |
Addition of bandwidth and Tx/Rx requirements |
|
R4-2201335 |
Equation Based for FR1 Minimum Output Power |
ZTE Corporation, Skyworks Solutions Inc. |
R4-2201336 |
Draft CR to TS38.101-1: Some corrections for the tables due to introduction of 35MHz_45MHz CBW |
ZTE Corporation, Skyworks Solutions Inc. |
5.26.1.2 |
NR-U 100MHz bandwidth |
|
R4-2200177 |
Further discussion on co-existence proposal between NR-U 100 MHz channel raster and Wi-Fi in 5 GHz (n46) |
Charter Communications, Inc |
R4-2200437 |
On intra-carrier guard bands for the 100MHz NR-U channel |
Apple |
R4-2200505 |
NR-U Punctured Channel SEM for 100 MHz Bandwidth |
CableLabs |
R4-2202156 |
Further discussion on co-existence proposal between NR-U 100 MHz channel raster and Wi-Fi in 5 GHz (n46) |
Charter Communications, Inc |
5.27 |
Introduction of bandwidth combination set 4 (BCS4) for NR |
|
R4-2202210 |
Email discussion summary for [101-bis-e][110] NR_BCS4_MSD_Inter_Band_ENDC |
Moderator (Huawei) |
R4-2202310 |
Email discussion summary for [101-bis-e][110] NR_BCS4_MSD_Inter_Band_ENDC |
Moderator (Huawei) |
5.27.1 |
UE RF requirements for BCS4/BCS5 |
|
R4-2200462 |
Handling of maximum aggregated channel bandwidth for BCS4/5 |
Nokia, Nokia Shanghai Bell |
R4-2200463 |
MSD table improvements |
Nokia, Nokia Shanghai Bell |
R4-2200464 |
Draft CR: Clarification on no simultaneous signalling of BCS4 and 5 for 38.101-1 |
Nokia, Nokia Shanghai Bell |
R4-2200465 |
Draft CR: Clarification on no simultaneous signalling of BCS4 and 5 for 38.101-3 |
Nokia, Nokia Shanghai Bell |
R4-2200619 |
Draft CR to TS 38.307 on Release independence of band combination set 4 and 5 |
ZTE Corporation |
R4-2201251 |
Discussion on simplifying extended MSD table |
Huawei, HiSilicon |
R4-2201252 |
Draft CR for 38.307 to introduce release independent method for BCS4/5 |
Huawei, HiSilicon |
R4-2201296 |
TP for TR 38.862 on the maximum aggregated bandwidth for intra-band CA with BCS4/BCS5 |
Xiaomi |
R4-2202040 |
Discussion on NR-CA and EN-DC MSD Table Simplifications |
Skyworks Solutions Inc. |
R4-2202287 |
WF on improvements to MSD table |
Huawei, HiSilicon |
5.27.2 |
Discussion of LS on NR CA capability for BCS5 (R2-1209073) |
|
R4-2201295 |
Reply LS on NR CA capability for BCS5 |
Xiaomi |
5.28.1 |
UE RF requirements |
|
R4-2201253 |
Draft CR for 38.101-3 to introduce MSD requirements for missing bandwidths |
Huawei, HiSilicon |
5.29 |
High-power UE operation for fixed-wireless/vehicle-mounted use cases in Band 12, Band 5, Band 13, Band n5, Band n13, and Band n71 |
|
R4-2202211 |
Email discussion summary for [101-bis-e][111] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
R4-2202311 |
Email discussion summary for [101-bis-e][111] LTE_NR_HPUE_FWVM |
Moderator (Nokia) |
5.29.1 |
General |
|
R4-2200703 |
TR 37.828 v0.1.0 |
Nokia, Nokia Shanghai Bell |
R4-2202288 |
TP to TR 37.828: Coexistence study for High-power UE Vs adjacent channel Public Safety operation for fixed-wireless/vehicle-mounted use cases in Band 5 and Band n5 |
Nokia, Nokia Shanghai Bell |
5.29.2.1 |
Coexistence study between B5 and adjacent bands |
|
R4-2200410 |
TP to TR 37.828: Coexistence study for High-power UE Vs adjacent channel Public Safety operation for fixed-wireless/vehicle-mounted use cases in Band 5 and Band n5 |
Nokia, Nokia Shanghai Bell |
5.29.3.2 |
UE Tx requirements (MOP, MPR, A-MPR, and ACLR) |
|
R4-2200704 |
MPR study for PC1 FWA device |
Nokia, Nokia Shanghai Bell |
5.30 |
High power UE (power class 2) for NR inter-band Carrier Aggregation with 2 bands downlink and 2 bands uplink |
|
R4-2200768 |
Draft TR 38.841 v0.6.0: High power UE for NR inter-band Carrier Aggregation with 2 bands downlink and x bands uplink (x =1,2) |
China Telecom |
R4-2200769 |
Draft CR to 38.101-1 Introduce RF requirements for HPUE CA with 2 bands downlink and x bands uplink (x =1,2) |
China Telecom |
R4-2202212 |
Email discussion summary for [101-bis-e][112] NR_PC2_SUL_CA_lowMSD |
Moderator (China Telecom) |
R4-2202312 |
Email discussion summary for [101-bis-e][112] NR_PC2_SUL_CA_lowMSD |
Moderator (China Telecom) |
5.30.1 |
UE RF requirements |
|
R4-2200304 |
DraftCR to 38.101-1 for HPUE CA with 2 bands downlink and x bands uplink (x =1,2) |
Verizon Denmark |
R4-2201225 |
Draft CR to 38.101-1 corrections on Tx power configuration on IMD requirement for high power UE inter-band CA |
Xiaomi |
R4-2201680 |
TP for TR 38.841 Addition of CA_n29-n77 |
AT&T |
R4-2201717 |
DraftCR to 38.101-1 for HPUE CA with 2 bands downlink and x bands uplink (x =1,2) |
Verizon, AT&T |
R4-2202041 |
Power Class notation for BCSs |
T-Mobile USA |
R4-2202042 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for DL CA_n41(2A) UL n41 |
T-Mobile USA |
R4-2202043 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n25 and n41 |
T-Mobile USA |
R4-2202044 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n41 and n66 |
T-Mobile USA |
R4-2202045 |
Draft CR for 38.101-1: Addition of PC2 and PC1.5 for combinations with n41 and n71 |
T-Mobile USA |
R4-2202290 |
Draft CR to 38.101-1 for HPUE CA with 2 bands downlink and x bands uplink (x =1,2) |
Verizon, AT&T |
5.31 |
High power UE (power class 2) for EN-DC with 1 LTE band + 1 NR TDD band |
|
R4-2202213 |
Email discussion summary for [101-bis-e][113] NR_PC2_EN-DC |
Moderator (Ericsson) |
R4-2202313 |
Email discussion summary for [101-bis-e][113] NR_PC2_EN-DC |
Moderator (Ericsson) |
5.31.1 |
UE RF requirements |
|
R4-2200305 |
TP for TR 37.826 for DL DC_48_n77 |
Verizon Denmark |
5.32 |
Power Class 2 UE for NR inter-band CA and SUL configurations with x (x>2) bands DL and y (y=1, 2) bands UL |
|
R4-2202020 |
MSD update needed for PC2 and PC1.5 UL configurations |
Skyworks Solutions Inc. |
5.33.1 |
UE RF requirements |
|
R4-2200303 |
DraftCR to add EN-DC PC2 band combinations with more than 2 bands |
Verizon Denmark |
R4-2200306 |
TP for TR 37.827 for DC_2-5_n2-n77 |
Verizon, Samsung |
R4-2200308 |
TP for TR 37.827 for DC_2-5_n66-n77 |
Verizon Denmark |
R4-2200309 |
TP for TR 37.827 for DC_2-5-66_n2-n77 |
Verizon Denmark |
R4-2200310 |
TP for TR 37.827 for DC_2-5-66_n66-n77 |
Verizon, Samsung |
R4-2200311 |
TP for TR 37.827 for DC_2-5-66_n77 |
Verizon, Samsung |
R4-2200313 |
TP for TR 37.827 for DC_2-13_n66-n77 |
Verizon, Samsung |
R4-2200314 |
TP for TR 37.827 for DC_2-13-66_n66-n77 |
Verizon, Samsung |
R4-2200315 |
TP for TR 37.827 for DC_2-13-66_n77 |
Verizon, Samsung |
R4-2200316 |
TP for TR 37.827 for DC_2-66_n66-n77 |
Verizon, Samsung |
R4-2200317 |
TP for TR 37.827 for DC_5-66_n2-n77 |
Verizon, Samsung |
R4-2200318 |
TP for TR 37.827 for DC_5-66_n66-n77 |
Verizon, Samsung |
R4-2200319 |
TP for TR 37.827 for DC_5-66_n77 |
Verizon, Samsung |
R4-2200320 |
TP for TR 37.827 for DC_13-66_n66-n77 |
Verizon, Samsung |
R4-2201684 |
DraftCR 38.101-3 Addition of PC2 EN-DC Combinations |
AT&T |
R4-2202291 |
DraftCR to add EN-DC PC2 band combinations with more than 2 bands |
Verizon |
5.35 |
Increasing UE power high limit for CA and DC |
|
R4-2202214 |
Email discussion summary for [101-bis-e][114] NR_Power_Limit_CA_DC |
Moderator (Qualcomm) |
R4-2202314 |
Email discussion summary for [101-bis-e][114] NR_Power_Limit_CA_DC |
Moderator (Qualcomm) |
5.35.2 |
Feasibility and impact study |
|
R4-2200454 |
Comparison between variants of “the sum method” |
Nokia, Nokia Shanghai Bell |
R4-2200494 |
Implementation aspects of increasing MOP for PC2 inter-band ULCA |
Skyworks Solutions Inc. |
R4-2200852 |
Increasing UE power high limit for CA and DC by existing signaling |
Ericsson |
R4-2200965 |
Further discussion on the increasing UE power high limit for CA and DC |
vivo |
R4-2201278 |
R17 UE power class high limit |
OPPO |
R4-2201334 |
Further discussion on increase UE maximum power for NR uplink inter band CA |
ZTE Corporation |
R4-2201836 |
On Increasing MOP for NR inter-band CA |
Huawei,HiSilicon |
5.35.3 |
UE RF requirements |
|
R4-2200440 |
UE maximum output power for inter-band UL CA |
Apple |
R4-2200455 |
UE RF requirements for the sum method |
Nokia, Nokia Shanghai Bell |
R4-2201229 |
Discussion on increasing UE maximum power high limit |
Xiaomi |
R4-2201265 |
RF requirements impact for Increased MOP for CA and DC |
InterDigital, Inc. |
R4-2201856 |
Higher output power for CA and DC |
Qualcomm Incorporated |
R4-2202404 |
WF on agreements for increasing MOP for CA and DC |
Qualcomm |
5.36 |
High power UE (power class 2) for NR FDD band |
|
R4-2202215 |
Email discussion summary for [101-bis-e][115] NR_PC2_UE_FDD |
Moderator (China Unicom) |
R4-2202292 |
WF on A-MPR for FDD PC2 HPUE |
Apple, Huawei, HiSilicon |
R4-2202293 |
WF on MSD requirements for FDD PC2 HPUE |
China Unicom |
R4-2202315 |
Email discussion summary for [101-bis-e][115] NR_PC2_UE_FDD |
Moderator (China Unicom) |
5.36.2 |
UE RF requirements |
|
R4-2200908 |
Hybrid duplex operation for PC2 FDD bands |
Apple |
R4-2201226 |
Discussion on HP UE for FDD bands |
Xiaomi |
5.36.2.2 |
A-MPR requirements |
|
R4-2200444 |
HPUE A-MPR Proposal for NS_05 |
Apple |
R4-2200445 |
HPUE A-MPR Proposal for NS_48 |
Apple |
R4-2200446 |
HPUE A-MPR Proposal for NS_49 |
Apple |
R4-2200447 |
HPUE A-MPR Proposal for NS_100 |
Apple |
R4-2201834 |
On A-MPR requirements for PC2 FDD bands |
Huawei,HiSilicon |
R4-2202008 |
A-MPR for Bandwidth Parts |
Lenovo, Motorola Mobility |
5.36.2.3 |
PC2 MSD requirements (investigation for HD-FDD) |
|
R4-2200441 |
NR FDD HPUE MSD and system performance analyses |
Apple |
R4-2200964 |
Further discussion on half duplex operation under HPUE |
vivo |
R4-2201070 |
MSD analysis for PC2 FDD UE |
LG Electronics Inc. |
R4-2201338 |
Discussion on HPUE FDD MSD |
ZTE Corporation |
R4-2201835 |
On MSD requirements for PC2 FDD bands |
Huawei,HiSilicon |
5.37 |
Additional NR bands for UL-MIMO |
|
R4-2202216 |
Email discussion summary for [101-bis-e][116] LTE_NR_Other_WI |
Moderator (Huawei) |
R4-2202294 |
WF on simultaneous Rx/Tx capability for FR1+FR1 FDD-TDD band combinations |
Huawei, HiSilicon |
R4-2202295 |
WF on simultaneous Rx/Tx capability for band pairs included in higher order band combinations |
NTT Docomo |
R4-2202316 |
Email discussion summary for [101-bis-e][116] LTE_NR_Other_WI |
Moderator (Huawei) |
5.37.1 |
UE RF requirements |
|
R4-2201759 |
Draft CR for n24 and n99 UL-MIMO PC3 |
Ligado Networks |
5.38 |
Downlink interruption for band combinations to conduct dynamic Tx Switching |
|
R4-2200770 |
Draft CR to 38.101-1 Introduce DL interruption clarification for CA conduting Tx Switching |
China Telecom |
5.39 |
Simultaneous Rx/Tx band combinations for CA, SUL, MR-DC and NR-DC |
|
R4-2200566 |
Clarification on per-band-pair simultaneous RxTx capability |
NTT DOCOMO INC. |
5.39.1 |
MSD threshold principle |
|
R4-2200354 |
Discussion on the simultaneous Rx/Tx capability for FR1+FR1 FDD-TDD band combination |
SoftBank Corp. |
R4-2201067 |
Discussion on simultaneous RxTx capability for FR1 FDD-TDD band combination |
Samsung |
R4-2201230 |
Discussion on principle for simultaneous Rx Tx band combinations for CA, SUL, MR-DC and NR-DC |
Xiaomi |
R4-2201340 |
Simultaneous Rx/Tx capability for FR1+FR1 FDD-TDD band combination |
ZTE Corporation |
R4-2201954 |
Further consideration on the MSD principle for FR1 FDD-TDD band combination |
Huawei, HiSilicon |
R4-2201955 |
TP for TR 38.839: Principles for simultaneous RxTx capability |
Huawei, HiSilicon |
5.39.2 |
FR2 band combinations with simultaneous Rx/Tx |
|
R4-2200567 |
View on FR2 simultaneous Tx/Rx discussion |
MediaTek Beijing Inc. |
R4-2201341 |
DRAFT CR to TS 38.101-2: On Simultaneous RxTx capability for FR2 inter-band CA |
ZTE Corporation |
R4-2201342 |
DRAFT CR to TS 38.101-2: On Simultaneous RxTx capability for FR2 inter-band CA |
ZTE Corporation |
R4-2201343 |
Draft CR to TS38.101-2[R17] On Simultaneous RxTx capability for FR2 inter-band CA_n257-n259 and CA_n258-n260 |
ZTE Corporation |
R4-2201956 |
Further consideration on the simultaneous Rx/Tx capability for FR2 TDD-TDD band combination |
Huawei, HiSilicon |
5.40 |
4Rx support for NR band n8 |
|
R4-2202217 |
Email discussion summary for [101-bis-e][117] NR_4Rx_Bn8_FWA |
Moderator (OPPO) |
R4-2202317 |
Email discussion summary for [101-bis-e][117] NR_4Rx_Bn8_FWA |
Moderator (OPPO) |
5.40.1 |
UE RF requirements (delta_R_IB,4Rx) |
|
R4-2201347 |
On band n8 support 4Rx |
ZTE Corporation |
R4-2201372 |
draft CR for 4 Rx antenna ports support of band n8 |
CHTTL |
5.40.2 |
Release independency |
|
R4-2201413 |
Discussion on release independent for 4Rx support for NR band |
CHTTL |
6.1.1 |
General |
|
R4-2200966 |
3GPP TS 38.151 v0.7.0 |
vivo |
R4-2200970 |
Discussion on framework for FR1 MIMO OTA performance |
vivo |
R4-2201920 |
Illustration of Device Orientations for Select Test Points |
Keysight Technologies UK Ltd |
R4-2202954 |
Email discussion summary for [101-bis-e][324] NR_MIMO_OTA |
Moderator (CAICT) |
R4-2203063 |
WF on MIMO OTA |
vivo, CAICT |
R4-2203064 |
TP to TS38.151 on FR1 Spatial Channel Model Validation |
Spirent Communications |
R4-2203065 |
Discussion on preliminary MU assessment for FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2203067 |
Framework for FR1 MIMO OTA lab alignment activity |
CAICT |
R4-2203096 |
Email discussion summary for [101-bis-e][324] NR_MIMO_OTA |
Moderator (CAICT) |
6.1.2.1 |
Performance Requirements for FR1 |
|
R4-2200572 |
On framework for PAD alignment of NR UE FR1 MIMO OTA |
Huawei, HiSilicon |
R4-2200576 |
FR1 MIMO OTA channel validation |
MediaTek Beijing Inc. |
R4-2200969 |
Pass/Fail limit for FR1 MIMO OTA lab alignment activity |
vivo |
R4-2201282 |
Commercial devices preparation and data handling |
OPPO |
R4-2201602 |
Framework for FR1 MIMO OTA lab alignment activity |
CAICT |
6.1.2.2 |
Performance Requirements for FR2 |
|
R4-2200580 |
FR2 MIMO OTA Simulation |
MediaTek Beijing Inc. |
R4-2200777 |
Discussion on FR2 MIMO OTA requirements |
Qualcomm Incorporated |
R4-2200778 |
Summary results for FR2 MIMO OTA simulation |
Qualcomm Incorporated |
R4-2201441 |
Discussion FR2 MIMO OTA performance requirements |
Huawei,HiSilicon |
6.1.2.3 |
MU assessment for FR1 and FR2 |
|
R4-2200779 |
Discussion on preliminary MU assessment for FR2 MIMO OTA |
Qualcomm Incorporated |
R4-2200968 |
Proposal for MU budget of FR1 MIMO OTA |
vivo |
R4-2203066 |
FR1 MIMO OTA Lab Alignment, Channel Model Validation |
Apple |
6.1.3.1 |
Testing parameters for Performance |
|
R4-2200780 |
TP on TS 38.151 for test parameters of FR2 performance |
Qualcomm Incorporated |
6.1.3.2 |
Optimization of test methodologies |
|
R4-2200731 |
Max downlink power verification of MIMO OTA test system |
Samsung |
R4-2200967 |
TP to TS38.151 on FR2 maximum downlink power and test procedure |
vivo |
6.1.3.3 |
Channel model validation |
|
R4-2200409 |
TP to TS38.151 on FR1 Spatial Channel Model Validation |
Spirent Communications |
R4-2200573 |
Further results on FR1 channel model validation |
Huawei, HiSilicon |
R4-2200832 |
FR1 channel model validation results for CMCC & BUPT joint lab |
CMCC BUPT |
R4-2200906 |
FR1 MIMO OTA Lab Alignment, Channel Model Validation |
Apple |
R4-2201494 |
Validation results and limits for FR1 CDL-C UMa channel model-v1 |
Xiaomi |
R4-2201591 |
FR1 MIMO OTA channel model validation results and views on PDP pass/fail limits |
CAICT |
R4-2201676 |
Reference Channel Emulation PDP for Validation Purposes for FR1 CDL-C UMa |
CAICT, CMCC, Keysight Technologies, Spirent Communications |
R4-2201919 |
Pass/Fail Limits for FR1 Channel Model Validation |
Keysight Technologies UK Ltd |
R4-2203045 |
Further results on FR1 channel model validation |
Huawei, HiSilicon |
R4-2203068 |
Pass/Fail Limits for FR1 Channel Model Validation |
Keysight Technologies UK Ltd |
R4-2203122 |
Validation results and limits for FR1 CDL-C UMa channel model-v1 |
Xiaomi |
6.2 |
Introduction of UE TRP (Total Radiated Power) and TRS (Total Radiated Sensitivity) requirements and test methodologies for FR1 (NR SA and EN-DC) |
|
R4-2202049 |
TR 38.834 v0.3.0 |
OPPO |
6.2.1 |
General and work plan |
|
R4-2200732 |
Discussion on hand phantom handling in FR1 TRP TRS |
Samsung |
R4-2200733 |
TP to TR 38.834 on band parameters |
Samsung |
R4-2200971 |
3GPP TS 38.161 v0.1.0 |
vivo |
R4-2200975 |
Discussion and Text Proposals on band parameters |
vivo |
R4-2200977 |
TP to TR 38.834 on Phantom definition |
vivo |
R4-2200981 |
Updated workplan of TRP TRS WI |
vivo |
R4-2201285 |
TP to TR 38.834 on multi antenna |
OPPO |
R4-2201606 |
Progress on MU and recommendations from RAN5#93-e |
ROHDE & SCHWARZ |
R4-2201649 |
TP to TR 38.834 on skeleton for Annex B |
ROHDE & SCHWARZ |
R4-2202955 |
Email discussion summary for [101-bis-e][325] FR1_TRP_TRS_Part1 |
Moderator (Vivo) |
R4-2203069 |
TP to TR 38.834 on multi antenna |
OPPO |
R4-2203070 |
WF on FR1 TRP TRS for UE with multi-antenna |
OPPO |
R4-2203073 |
Discussion and Text Proposals on band parameters |
vivo |
R4-2203075 |
TP to TR 38.834 on Phantom definition |
vivo |
R4-2203076 |
WF on FR1 TRP TRS |
vivo |
R4-2203077 |
TP work split for TS 38.161 drafting |
vivo, Huawei, CAICT, Xiaomi, Samsung |
R4-2203097 |
Email discussion summary for [101-bis-e][325] FR1_TRP_TRS_Part1 |
Moderator (Vivo) |
6.2.2 |
Test methodology |
|
R4-2200935 |
TP to TR 38.834 on performance metrics |
CAICT |
6.2.2.1 |
SA test methodology |
|
R4-2200450 |
TP to TR 38.834 on P-MPR handling |
Apple |
R4-2200972 |
TP to TR 38.834 on SA TRP TRS test procedure |
vivo, CAICT |
R4-2203071 |
TP to TR 38.834 on SA TRP TRS test procedure |
vivo, CAICT |
6.2.2.2 |
EN-DC test methodology |
|
R4-2200449 |
Views on EN-DC methodology |
Apple |
R4-2200574 |
on remaining details of EN-DC TRP test configuration |
Huawei, HiSilicon |
R4-2200734 |
Discussion on ENDC power splitting for TRS |
Samsung |
R4-2200785 |
Discussion on EN-DC test methodology |
Qualcomm Incorporated |
R4-2200973 |
Discussion and Text Proposals on EN-DC TRP TRS test procedure |
vivo, CAICT |
R4-2201495 |
On EN-DC power split for TRS |
Xiaomi |
R4-2203072 |
Discussion and Text Proposals on EN-DC TRP TRS test procedure |
vivo, CAICT |
6.2.2.3 |
UE with multiple antennas test methodology |
|
R4-2200786 |
Discussion on TAS ON test methodology |
Qualcomm Incorporated |
R4-2201284 |
On the influence factors of Tx antenna switch |
OPPO |
R4-2201286 |
Consideration on Tx Diversity |
OPPO |
R4-2202956 |
Email discussion summary for [101-bis-e] [326] FR1_TRP_TRS_Part2 |
Moderator (OPPO) |
R4-2203098 |
Email discussion summary for [101-bis-e] [326] FR1_TRP_TRS_Part2 |
Moderator (OPPO) |
6.2.2.4 |
Test time reduction |
|
R4-2200980 |
Discussion on alternative test method for TRP TRS testing time reduction |
vivo |
6.2.3 |
Performance requirements |
|
R4-2201283 |
On hand phantom selection for Rel-17 requirement |
OPPO |
6.2.3.1 |
Framework for lab alignment and requirements |
|
R4-2200448 |
Further views on manufacturing tolerances |
Apple |
R4-2200575 |
On framework for NR UE TRP/TRS lab alignment and requirements |
Huawei, HiSilicon |
R4-2200976 |
Working procedure for TRP TRS requirement development |
vivo |
R4-2203074 |
Working procedure for TRP TRS requirement development |
vivo |
6.2.3.2 |
SA requirements |
|
R4-2200974 |
TP to TS 38.161 on requirement applicability |
vivo |
6.3.1 |
General |
|
R4-2200019 |
draft CR: UL MIMO coherence for Tx switching |
China Telecom |
R4-2200499 |
Requirement and signaling aspect of features requiring two transmit paths |
Skyworks Solutions Inc. |
R4-2200611 |
Discussion on capability signalling for HPUE NR DC with UE supporting TxD |
MediaTek Inc. |
R4-2200612 |
Draft LS on signalling clarification of NR CA/DC power class in R17 |
MediaTek Inc. |
R4-2200958 |
TP for TR 38.837 on Power Class clarification |
vivo |
R4-2201228 |
PC2 PA configuration and signalling |
Xiaomi |
R4-2201590 |
3GPP TR 38.837 v0.3.0 |
vivo |
R4-2202218 |
Email discussion summary for [101-bis-e][118] NR_RF_FR1_enh_IntraHPUE |
Moderator (Huawei) |
R4-2202297 |
draft CR: UL MIMO coherence for Tx switching |
China Telecom |
R4-2202300 |
WF on PC2 intra-band contiguous UL CA with UL MIMO |
Huawei, HiSilicon |
R4-2202318 |
Email discussion summary for [101-bis-e][118] NR_RF_FR1_enh_IntraHPUE |
Moderator (Huawei) |
R4-2202340 |
WF on PC2 intra-band NC UL CA for FR1 |
Skyworks |
R4-2202341 |
WF on SCell dropping |
vivo |
6.3.2.2 |
HPUE for TDD intra-band contiguous UL CA |
|
R4-2200334 |
Requirements for different architectures and their capabilities |
Qualcomm Incorporated |
R4-2200497 |
Signaling for contiguous ULCA cases |
Skyworks Solutions Inc. |
R4-2201593 |
Draft CR TS 38.101-1 R17: Introduction of PC2 contiguous ULCA MPR for 2Tx |
Skyworks Solutions Inc. |
6.3.2.3 |
HPUE for TDD intra-band non-contiguous UL CA |
|
R4-2200335 |
draft CR to remove dualPA from Rel-16 specs |
Qualcomm Incorporated |
R4-2200336 |
2CC LO location reportting and dualPA capability in rel-16 |
Qualcomm Incorporated |
R4-2200498 |
Requirement and signaling aspect of non-contiguous ULCA |
Skyworks Solutions Inc. |
R4-2201674 |
Draft CR TS 38.101-1 R17: Addition of PC2 non-contiguous ULCA MPR requirements |
Skyworks Solutions Inc. |
R4-2201943 |
Big CR for PC2 intra-band non-contiguous UL CA |
Huawei, HiSilicon, Qualcomm |
R4-2201944 |
Consideration on signalling to differentiate MPR for different architectures |
Huawei, HiSilicon |
R4-2202298 |
Big CR for PC2 intra-band non-contiguous UL CA |
Huawei, HiSilicon, Qualcomm, Skyworks |
6.3.2.4 |
Intra-band UL contiguous CA for UL MIMO (n41C and n78C) |
|
R4-2200493 |
Signalling on PC2 intra-band NC UL CA for FR1 |
Nokia, Nokia Shanghai Bell |
R4-2200495 |
MPR for PC2 intra-band contiguous ULCA&MIMO 26+23 case |
Skyworks Solutions Inc. |
R4-2200956 |
Discussion on MPR applicability and reference architectures for CA +UL MIMO and TxD |
vivo |
R4-2201069 |
MPR and capability signaling for 2Tx PC2 intra-band contiguous UL CA with UL MIMO |
Samsung |
R4-2201270 |
R17 FR1 UL CA and UL MIMO MPR |
OPPO |
R4-2201800 |
DraftCR on TS 38.101-1 on ULCA + ULMIMO |
ZTE Wistron Telecom AB |
R4-2201946 |
On RF requirements for PC2 intra-band UL CA with UL MIMO |
Huawei, HiSilicon |
R4-2201947 |
Big CR for TS 38.101-1: contiguous CA with UL MIMO for power class 2 |
Huawei, HiSilicon |
R4-2202299 |
Big CR for TS 38.101-1: contiguous CA with UL MIMO for power class 2 |
Huawei, HiSilicon |
6.3.2.5 |
Solution preventing transmission power dropping on cell with lower priority |
|
R4-2200337 |
Solution for SCell dropping |
Qualcomm Incorporated |
R4-2200957 |
Further discussion on Scell dropping |
vivo |
6.3.2.5.1 |
FR1 related |
|
R4-2200853 |
Further details on resolving the Scell dropping (power prioritization) problem by power limits |
Ericsson |
R4-2200854 |
Introduction of power limits for serving cells of UL CA |
Ericsson |
R4-2201068 |
Discussion on transmission power dropping on cell with low priority |
Samsung |
R4-2201945 |
On SCell dropping |
Huawei, HiSilicon |
6.3.2.5.2 |
FR2 related |
|
R4-2200855 |
Introduction of power limits for serving cells of UL CA |
Ericsson |
6.4.1 |
General |
|
R4-2200699 |
TR38.851 v0.3.0 |
Nokia, Nokia Shanghai Bell |
R4-2202219 |
Email discussion summary for [101-bis-e][119] NR_RF_FR2_enh2_Part_1 |
Moderator (Nokia) |
R4-2202319 |
Email discussion summary for [101-bis-e][119] NR_RF_FR2_enh2_Part_1 |
Moderator (Nokia) |
R4-2202342 |
WF on FR2 DL CA |
Nokia |
R4-2202343 |
WF on FR2 UL CA |
Qualcomm |
6.4.2.1 |
Inter-band DL CA requirements |
|
R4-2200361 |
Sensitivity requirements for inter-band CA with CBM |
NTT DOCOMO, INC. |
R4-2200940 |
Discussion on introducation of Fs, inter_CBM |
vivo |
R4-2201970 |
dCR to 38.101-2 on requirements for UEs that support inter-band CA with CBM |
Nokia, Nokia Shanghai Bell, Qualcomm Incorporated |
6.4.2.1.1 |
CA configurations within the same frequency group based on CBM |
|
R4-2200362 |
UE capability for CA within same frequency group with CBM |
NTT DOCOMO, INC. |
R4-2200466 |
UE requirements for CBM for the same frequency group |
Sony, Ericsson |
R4-2200554 |
Discussion on CBM based inter-band DL CA within same frequency group |
LG Electronics |
R4-2200579 |
Reference signal and Fs_intern_CBM of FR2 inter-band DL CA within same frequency group based on CBM |
MediaTek Beijing Inc. |
R4-2200939 |
Discussion on CBM within same frequency group |
vivo |
R4-2201275 |
R17 FR2 CBM inter-band DL CA |
OPPO |
R4-2201337 |
Discussion on CBM for FR2 Inter-band DL CA |
ZTE Corporation |
R4-2201968 |
On delta(RIB) for n258+n261 DL inter-CA |
Qualcomm Incorporated |
6.4.2.1.2 |
CA configurations between different frequency groups based on CBM |
|
R4-2200439 |
Views on FR2 inter-band DL CA CBM for different band groups |
Apple |
R4-2200467 |
Requirements for CBM UEs between different frequency group |
Sony, Ericsson |
R4-2200577 |
Reference signal of FR2 inter-band DL CA between different frequency groups based on CBM |
MediaTek Beijing Inc. |
R4-2200700 |
TP to TR 38.851: Agreements made for CA configurations between frequency groups using CBM |
Nokia, Nokia Shanghai Bell |
R4-2200735 |
Discussion on requirements of FR2 inter-band DL CA |
Samsung |
R4-2200941 |
Discussion on CBM between different frequency group |
vivo |
R4-2201299 |
Rx requirements for inter-band DL CA with CBM |
Xiaomi |
R4-2201969 |
On delta(RIB) for DL inter-CA with CBM in n260+n261 |
Qualcomm Incorporated |
6.4.2.1.4 |
Rx beam switch value |
|
R4-2200701 |
Discussion on UE Rx beam switch delay |
Nokia, Nokia Shanghai Bell |
R4-2200945 |
Discussion on Rx beam switch time |
vivo |
R4-2201594 |
Discussion on UE Rx beam switch delay |
Nokia |
6.4.2.2.1 |
Inter-band UL CA for two bands |
|
R4-2200345 |
FR2 inter-band UL CA framework |
Nokia, Nokia Shanghai Bell |
R4-2200468 |
UE UL CA requirements based on IBM |
Sony, Ericsson |
R4-2200736 |
Discussion on requirements of FR2 inter-band UL CA |
Samsung |
R4-2200942 |
Discussion on inter-band UL CA |
vivo |
R4-2201276 |
R17 FR2 Inter-band UL CA requirements |
OPPO |
R4-2201291 |
Discussion on inter-band UL CA requirements |
ZTE Corporation |
R4-2201300 |
Tx requirements for inter-band UL CA between different frequency groups based on IBM |
Xiaomi |
6.4.2.2.2 |
CA configuration CA_n257A-n259A based on IBM |
|
R4-2200346 |
TP to TR 38.851 to introduce FR2 UL CA_n257A-n259A |
Nokia, Nokia Shanghai Bell |
R4-2200555 |
RF requirements for CA_n257A_n259A based on IBM |
LG Electronics |
R4-2200569 |
View on factor of FR2 inter-band UL CA relaxation |
MediaTek Beijing Inc. |
R4-2201292 |
Discussion on relaxation value X&Y for CA_n257A_n259A |
ZTE Corporation |
R4-2201967 |
On UL power for FR2 inter-band ULCA |
Qualcomm Incorporated |
6.4.3 |
UL gaps for self-calibration and monitoring |
|
R4-2200353 |
Discussion of UL gap in FR2 RF enhancement for RAN2 LS |
Mediatek India Technology Pvt. |
R4-2201693 |
Discussion on LS on UL gap in FR2 RF enhancement |
Nokia, Nokia Shanghai Bell |
R4-2202220 |
Email discussion summary for [101-bis-e][120] NR_RF_FR2_enh2_Part_2 |
Moderator (Apple) |
R4-2202320 |
Email discussion summary for [101-bis-e][120] NR_RF_FR2_enh2_Part_2 |
Moderator (Apple) |
R4-2202344 |
WF on UL gap for FR2 |
Apple |
R4-2202345 |
Reply LS to RAN2 on UL gap in FR2 RF enhancement |
Apple |
R4-2202417 |
WF on UL gap for FR2 |
Apple |
R4-2202419 |
Reply LS to RAN2 on UL gap in FR2 RF enhancement |
Apple |
R4-2202420 |
LS to RAN2 on UL gap in FR2 RF enhancement |
Apple |
6.4.3.1 |
UE Tx power management |
|
R4-2200253 |
UL gaps for Tx power management RF aspect |
Apple |
R4-2200255 |
Draft CR for UL gap for Tx power management RF aspect |
Apple |
R4-2200383 |
Requirements and test cases of UE FR2 UL Gap for UE Tx power enhancement |
Nokia, Nokia Shanghai Bell |
R4-2200589 |
Discussion on UL gap for Tx power management |
ZTE Corporation |
R4-2200856 |
On UE Tx power management for MPE compliance |
Ericsson, Sony |
R4-2200943 |
Discussion and reply LS on FR2 UL gap |
vivo |
R4-2201274 |
R17 FR2 UL gap for power management |
OPPO |
R4-2201443 |
Discussion on Tx power management |
Huawei,HiSilicon |
6.4.3.2 |
Coherent UL-MIMO |
|
R4-2200254 |
UL gaps for coherent UL MIMO |
Apple |
R4-2201442 |
Draft CR to 38.101-2 on requirements for coherent UL MIMO |
Huawei,HiSilicon |
R4-2201444 |
Discussion on UL coherent MIMO |
Huawei,HiSilicon |
6.4.4 |
DC location for intra-band UL CA with > 2 CCs for both FR2 and FR1 |
|
R4-2200333 |
Further details and optimizations on DC location |
Qualcomm Incorporated |
R4-2200456 |
Handling of multiple DC locations for intra-band configuration |
Nokia, Nokia Shanghai Bell |
R4-2200944 |
Discussion on DC location |
vivo |
R4-2201273 |
R17 FR2 DC reporting |
OPPO |
R4-2201959 |
Further study on DC location reporting |
Huawei, HiSilicon |
R4-2202221 |
Email discussion summary for [101-bis-e][121] NR_RF_FR2_enh2_Part_3 |
Moderator (Vivo) |
R4-2202321 |
Email discussion summary for [101-bis-e][121] NR_RF_FR2_enh2_Part_3 |
Moderator (Vivo) |
R4-2202346 |
WF on DC-Location |
vivo |
R4-2202347 |
WF on FR2 CA BW classes |
Xiaomi |
6.4.5.1 |
New FR2 CA BW classes |
|
R4-2200857 |
FR2 bandwidth classes covering up to 1600 MHz aggregated bandwidth with mixed carrier bandwidths |
Ericsson |
R4-2200858 |
FR2 CA BW classes up to 1600 MHz aggregated BW with mixed channel bandwidths |
Ericsson |
R4-2200909 |
Alternatives of FR2 new CA BW classes |
Apple |
R4-2201297 |
Draft CR for TS 38.101-2 to introduction of FR2 new CA BW classesV, MF,ME, MD and MA |
Xiaomi |
6.4.5.2 |
Fallback group |
|
R4-2200302 |
FR2 bandwidth class and fallback group |
Verizon, Qualcomm, MediaTek |
R4-2200620 |
Further considerations on FR2 fallback group |
ZTE Corporation |
R4-2201298 |
Discussion on fallback group for FR2 new CA BW classes |
Xiaomi |
6.4.6 |
RRM core requirements |
|
R4-2201536 |
Draft Big CR: RRM requirements for Rel-17 NR FR2 Inter-band CA |
Nokia, Nokia Shanghai Bell |
R4-2202553 |
Email discussion summary for [101-bis-e][202] NR_RF_FR2_enh2_RRM |
Moderator (Nokia) |
R4-2202719 |
Email discussion summary for [101-bis-e][202] NR_RF_FR2_enh2_RRM |
Moderator (Nokia) |
6.4.6.1.1 |
MRTD requirements |
|
R4-2200391 |
Further considering on remaining issues for RRM requirements for inter-band DL CA in NR FR2 |
vivo |
R4-2200425 |
MRTD requirements for CBM based Inter-band DL CA |
Qualcomm Incorporated |
R4-2200559 |
Discussion on MRTD for FR2 inter-band CA based on CBM |
LG Electronics |
R4-2200927 |
Discussion on CBM MRTD requirement for FR2 inter-band DL CA |
MediaTek inc. |
R4-2201129 |
MRTD requirements for FR2 inter-band DL CA enhancements |
OPPO |
R4-2201537 |
discussion on MRTD for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2201538 |
draftCR on MRTD for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2201588 |
Timing requirements for inter-band DL CA |
Ericsson |
R4-2201589 |
Timing requirements for inter-band DL CA |
Ericsson |
R4-2201607 |
Discussion on MRTD requirements for FR2 inter-band DL CA with CBM |
Huawei, Hisilicon |
R4-2202581 |
WF on RRM requirements for FR2 Inter-band DL CA and UL CA |
Nokia |
R4-2202582 |
draftCR on MRTD for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2202583 |
Timing requirements for inter-band DL CA |
Ericsson |
6.4.6.1.2 |
Other RRM requirements |
|
R4-2200426 |
RRM requirements for CBM based Inter-band DL CA |
Qualcomm Incorporated |
R4-2200742 |
Other RRM requirements for FR2 inter-band DL CA requirements for CBM |
ZTE Corporation |
R4-2200928 |
Discussion on CBM RRM requirements for FR2 inter-band DL CA |
MediaTek inc. |
R4-2200929 |
Introduction of SCell activation delay requirement for FR2 inter-band CA with common beam management |
MediaTek inc. |
R4-2201130 |
Other RRM requirements for FR2 inter-band DL CA enhancements |
OPPO |
R4-2201373 |
Discussion on RRM requirements of inter-band DL CA for CBM UE |
Ericsson |
R4-2201374 |
Draft CR on scheduling restriction for FR2 inter-band DL CA for CBM UE |
Ericsson |
R4-2201539 |
discussion on other RRM requirements for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2201540 |
draftCR on measurement restriction for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2201608 |
Discussion on other RRM requirements for FR2 inter-band DL CA with CBM |
Huawei, Hisilicon |
R4-2201609 |
DraftCR on interruption requirements for FR2 inter-band CA with CBM |
Huawei, Hisilicon |
R4-2202584 |
Introduction of SCell activation delay requirement for FR2 inter-band CA with common beam management |
MediaTek inc. |
R4-2202585 |
Draft CR on scheduling restriction for FR2 inter-band DL CA for CBM UE |
Ericsson |
R4-2202586 |
draftCR on measurement restriction for CBM inter-band FR2 DL CA |
Nokia, Nokia Shanghai Bell |
R4-2202587 |
DraftCR on interruption requirements for FR2 inter-band CA with CBM |
Huawei, Hisilicon |
6.4.6.2 |
Inter-band UL CA for IBM |
|
R4-2201131 |
Inter-band UL CA requirements for IBM |
OPPO |
R4-2201375 |
Discussion on RRM requirements for inter-band UL CA for IBM UE |
Ericsson |
R4-2201376 |
Draft CR on RRM requirements for FR2 inter-band UL CA for IBM UE |
Ericsson |
R4-2201541 |
draftCR on RRM requirements for IBM inter-band FR2 UL CA |
Nokia, Nokia Shanghai Bell |
R4-2202588 |
Draft CR on RRM requirements for FR2 inter-band UL CA for IBM UE |
Ericsson |
R4-2202589 |
draftCR on RRM requirements for IBM inter-band FR2 UL CA |
Nokia, Nokia Shanghai Bell |
6.4.6.3 |
UL gaps for self-calibration and monitoring |
|
R4-2200256 |
UL gaps for Tx power management RRM aspect and draft reply LS |
Apple |
R4-2200257 |
Draft CR for UL gap for Tx power management RRM aspect |
Apple |
R4-2200384 |
Network impact of UE FR2 UL Gap for UE Tx power enhancements |
Nokia, Nokia Shanghai Bell |
R4-2200427 |
UL gaps for self-calibration and monitoring |
Qualcomm Incorporated |
R4-2200590 |
Discussion on RRM impact of UL gap for Tx power management |
ZTE Corporation |
R4-2200605 |
Discussion on RRM impacts of UL gaps for self-calibration and monitoring |
vivo |
R4-2201377 |
Discussion on UL gaps for self calibration and monitoring |
Ericsson |
6.5.1 |
General |
|
R4-2202957 |
Email discussion summary for [101-bis-e][301] NR_Repeater_General |
Moderator (Qualcomm) |
R4-2203021 |
WF on System Parameters |
Ericsson |
R4-2203022 |
WF on TDD Repeater Switching |
Qualcomm |
R4-2203023 |
WF on Repeater Specifications |
Nokia |
R4-2203046 |
TP for TS 38.106:Clause 4 general |
CATT |
R4-2203047 |
TP for TS 38.106:Clause 5 operating bands |
CATT |
R4-2203048 |
TP for TS 38.106:ON OFF mask |
CATT |
R4-2203099 |
Email discussion summary for [101-bis-e][301] NR_Repeater_General |
Moderator (Qualcomm) |
6.5.1.1 |
System parameters |
|
R4-2200086 |
TP for TS 38.106:Clause 4 general |
CATT |
R4-2200087 |
TP for TS 38.106:Clause 5 operating bands |
CATT |
R4-2200089 |
Discussion of co-location requirements for multi-band repeaters |
CATT |
R4-2200818 |
Discussion on co-located requirements for FR1 NR repeater |
CMCC |
R4-2201289 |
Discussion on co-location requirement for multi-band repeaters |
ZTE Corporation |
6.5.1.3 |
TDD repeater switching requirements |
|
R4-2200090 |
Discussion of TDD switching requirements |
CATT |
R4-2200091 |
TP for TS 38.106:ON OFF mask |
CATT |
R4-2200821 |
Discussion on switching requirements |
CMCC |
R4-2201290 |
Discussion on repeater switching requirement and power transients |
ZTE Corporation |
R4-2201526 |
Repeaters TDD aspects |
Ericsson |
R4-2201544 |
Discussion on repeater switching requirements |
NEC |
R4-2201656 |
TDD repeater switching requirements |
Nokia, Nokia Shanghai Bell |
6.5.1.4 |
Others |
|
R4-2200088 |
Proposal to remove Annex A from the core spec |
CATT |
R4-2201529 |
Draft TP to TS 38.106: Frequency stability and out of band gain requirements |
Ericsson |
R4-2201657 |
Reference points and regional requirements for NR repeaters |
Nokia, Nokia Shanghai Bell |
R4-2201932 |
Repeater OTA declarations and specification points |
Huawei |
6.5.2 |
Conductive RF core requirements |
|
R4-2201930 |
TP to TS 38.106 6.1 and 6.2 |
Huawei |
R4-2202958 |
Email discussion summary for [101-bis-e][302] NR_Repeater_RF_Part1 |
Moderator (CMCC) |
R4-2203024 |
WF on OOB gain and ACRR requirement for FR1 |
Ericsson |
R4-2203025 |
WF on NF equivalent requirement for FR1 |
Nokia |
R4-2203026 |
WF on other conducted requirements |
CMCC |
R4-2203100 |
Email discussion summary for [101-bis-e][302] NR_Repeater_RF_Part1 |
Moderator (CMCC) |
6.5.2.1 |
Transmitted power related requirements |
|
R4-2200178 |
Views on the requirements to avoid interference of NR repeater for UL |
NTT DOCOMO, INC. |
R4-2200822 |
Discussion on repeater power related conducted requirements |
CMCC |
R4-2201459 |
Further discussions on power related requirements for conducted repeater |
ZTE Corporation |
R4-2201532 |
Repeater conducted power requirements |
Ericsson |
R4-2201658 |
Conducted power related requirements consideration for NR-Repeaters |
Nokia, Nokia Shanghai Bell |
6.5.2.2 |
Emission requirements |
|
R4-2200092 |
Discussion of remaining issues for FR1 emission requirements |
CATT |
R4-2200823 |
Discussion on repeater emission related conducted requirements |
CMCC |
R4-2201460 |
Further discussions on emission related requirements for conducted repeater |
ZTE Corporation |
R4-2201528 |
Repeater conducted emissions requirements |
Ericsson |
R4-2201654 |
TP to TS 38.106 clause 6.5 Unwanted emissions conducted |
Nokia, Nokia Shanghai Bell |
R4-2201660 |
Repeater conducted unwanted emissions |
Nokia, Nokia Shanghai Bell |
R4-2201933 |
Repeater FR1 OOB gain and ACRR |
Huawei |
R4-2201935 |
FR1 inband passband OBUE requirements and NF requirements |
Huawei |
6.5.2.3 |
Others |
|
R4-2200093 |
Discussion of out of band gain and ACRR requirements for FR1 |
CATT |
R4-2200819 |
Discussion on other RF conducted requirements for NR repeater |
CMCC |
R4-2200825 |
TP to TS 38.106 conducted EVM and input IMD |
CMCC |
R4-2201461 |
Further discussions on other requirements of conducted repeater |
ZTE Corporation |
R4-2201527 |
Repeater conducted requirements |
Ericsson |
R4-2201661 |
Low-power EVM and OOB gain considerations for FR1 NR Repeaters |
Nokia, Nokia Shanghai Bell |
R4-2201934 |
Discuss repeater co-location requirements |
Huawei |
6.5.3 |
Radiated RF core requirements |
|
R4-2201931 |
TP to TS 38.106 9.1and 9.2 |
Huawei |
R4-2202959 |
Email discussion summary for [101-bis-e][303] NR_Repeater_RF_Part2 |
Moderator (CATT) |
R4-2203027 |
WF on NR Repeater radiated requirements |
Huawei |
R4-2203101 |
Email discussion summary for [101-bis-e][303] NR_Repeater_RF_Part2 |
Moderator (CATT) |
6.5.3.1 |
Transmitted power related requirements |
|
R4-2201462 |
Further discussions on power related requirements for conducted repeater |
ZTE Corporation |
R4-2201659 |
Radiated power related requirements consideration for NR-Repeaters |
Nokia, Nokia Shanghai Bell |
6.5.3.2 |
Emission requirements |
|
R4-2200824 |
Discussion on repeater emission related radiated requirements |
CMCC |
R4-2201463 |
Further discussions on emission related requirements for radiated repeater |
ZTE Corporation |
R4-2201531 |
Repeaters radiated emissions requirements |
Ericsson |
R4-2201655 |
TP to TS 38.106 clause 7.5 Unwanted emissions radiated |
Nokia, Nokia Shanghai Bell |
R4-2201662 |
Repeater radiated unwanted emissions |
Nokia, Nokia Shanghai Bell |
R4-2201936 |
FR2 inside passband OBUE requirement and NF |
Huawei |
R4-2201937 |
Repeater FR2 OOB gain and ACRR |
Huawei |
6.5.3.3 |
Others |
|
R4-2200094 |
Discussion of out of band gain and ACRR requirements for FR2 |
CATT |
R4-2200820 |
Discussion on other RF radiated requirements for NR repeater |
CMCC |
R4-2200826 |
TP to TS 38.106 radiated EVM and input IMD |
CMCC |
R4-2201464 |
Further discussions on other requirements of radiated repeater |
ZTE Corporation |
R4-2201530 |
Repeaters radiated requirements |
Ericsson |
R4-2201663 |
Signal quality and OOB gain considerations for FR2 NR Repeaters |
Nokia, Nokia Shanghai Bell |
R4-2201938 |
FR2 input IM requirements |
Huawei |
6.5.4 |
EMC core requirements |
|
R4-2200696 |
Discussion on test conditions and performance assessment for NR repeater EMC tests |
ZTE |
R4-2200697 |
TP to TS38.114: References |
ZTE |
R4-2200730 |
TS38.114V0.2.0 to capture RAN4#101-bis agreements |
ZTE |
R4-2202960 |
Email discussion summary for [101-bis-e][304] NR_Repeater_EMC |
Moderator (ZTE) |
R4-2202986 |
TP to TS38.114: References |
ZTE |
R4-2202987 |
WF on NR repeater EMC testing |
ZTE |
R4-2203102 |
Email discussion summary for [101-bis-e][304] NR_Repeater_EMC |
Moderator (ZTE) |
6.6.4 |
BS RF conformance testing |
|
R4-2200134 |
Discussion on BS RF conformance testing for 1024QAM for NR FR1 |
CATT |
R4-2200135 |
Draft CR for 37.145-1 on BS RF conformance testing for 1024QAM for NR FR1 |
CATT |
R4-2201458 |
Draft CR to TS 38.141-1: Introduction of 1024 QAM in FR1 |
ZTE Corporation |
R4-2201489 |
CR to TS 38.141-2: Introduction of 1024 QAM in FR1 |
Ericsson |
R4-2201514 |
Test procedure for support of 1024QAM |
Huawei, HiSilicon |
R4-2201664 |
On 1024QAM for NR BS conformance tests |
Nokia, Nokia Shanghai Bell |
R4-2201665 |
Draft CR to TS 37.145-2 with 1024QAM introduction |
Nokia, Nokia Shanghai Bell |
R4-2202961 |
Email discussion summary for [101-bis-e][305] NR_DL1024QAM_RF |
Moderator (Ericsson) |
R4-2202995 |
Draft CR for 37.145-1 on BS RF conformance testing for 1024QAM for NR FR1 |
CATT |
R4-2202996 |
Draft CR to TS 38.141-1: Introduction of 1024 QAM in FR1 |
ZTE |
R4-2202998 |
draftCR to TS 38.141-2: Introduction of 1024 QAM in FR1 |
Ericsson |
R4-2202999 |
Draft CR to TS 37.145-2 with 1024QAM introduction |
Nokia |
R4-2203000 |
Draft CR for 37.141 on BS RF conformance testing for 1024QAM for NR FR1 |
CATT |
R4-2203103 |
Email discussion summary for [101-bis-e][305] NR_DL1024QAM_RF |
Moderator (Ericsson) |
6.6.5 |
Demodulation and CSI requirements |
|
R4-2202962 |
Email discussion summary for [101-bis-e][312] NR_DL1024QAM_Demod_NWM |
Moderator (Huawei) |
R4-2203104 |
Email discussion summary for [101-bis-e][312] NR_DL1024QAM_Demod_NWM |
Moderator (Huawei) |
6.6.5.1 |
General |
|
R4-2201427 |
Summary of PDSCH simulation results for DL 1024QAM in FR1 |
Ericsson |
R4-2201719 |
Simulation Results and views on 1024QAM FR1 UE Demod Tests |
Qualcomm Incorporated |
R4-2203044 |
Way forward for NR DL1024QAM demodulation and CQI reporting requirements |
Ericsson |
6.6.5.2 |
PDSCH requirements |
|
R4-2200265 |
Discussion on PDSCH demod requirements with 1KQAM |
Apple |
R4-2200376 |
Discussion on the PDSCH requirements for 1024QAM |
MediaTek inc. |
R4-2201011 |
Discussion and simulation results on 1024QAM PDSCH |
Huawei,HiSilicon |
R4-2201428 |
UE demodulation requirements for DL 1024QAM |
Ericsson |
R4-2201783 |
Discussion on PDSCH requirements for DL 1024QAM in FR1 |
Intel Corporation |
R4-2202980 |
UE demodulation requirements for DL 1024QAM |
Ericsson |
6.6.5.3 |
SDR requirements |
|
R4-2200266 |
Discussion on SDR requirements with 1KQAM |
Apple |
R4-2201012 |
Discussion and simulation results on 1024QAM SDR |
Huawei,HiSilicon |
R4-2201429 |
SDR requirements for DL 1024QAM |
Ericsson |
R4-2201784 |
Discussion on SDR requirements for DL 1024QAM in FR1 |
Intel Corporation |
6.6.5.4 |
CQI requirements |
|
R4-2201013 |
Discussion and simulation results on 1024QAM CSI |
Huawei,HiSilicon |
R4-2201430 |
CQI reporting requirements for DL 1024QAM |
Ericsson |
6.7 |
UE RF requirements for Transparent Tx Diversity (TxD) for NR |
|
R4-2202222 |
Email discussion summary for [101-bis-e][122] NR_TxD |
Moderator (Qualcomm) |
R4-2202322 |
Email discussion summary for [101-bis-e][122] NR_TxD |
Moderator (Qualcomm) |
6.7.1 |
General |
|
R4-2201941 |
Big CR for TS 38.101-1 Tx diversity requirements |
Huawei, HiSilicon, Qualcomm, vivo |
R4-2202974 |
Email discussion summary for [101-bis-e][310] NR_eIAB |
Moderator (Samsung) |
R4-2203116 |
Email discussion summary for [101-bis-e][310] NR_eIAB |
Moderator (Samsung) |
6.7.2 |
UE RF requirements for phase 1 (38.101-1) |
|
R4-2201772 |
Draft CR TS 38.101-1 R17: moving 2Tx MPR to clause 6.2D and amending PC2 2TX MPR |
Skyworks Solutions Inc. |
R4-2202348 |
TP for TR 38.837 on Power Class clarification |
Vivo |
R4-2202349 |
Draft CR TS 38.101-1 R17: moving 2Tx MPR to clause 6.2D and amending PC2 2TX MPR |
Skyworks Solutions Inc., Huawei, HiSilicon, Qualcomm, LGE |
R4-2202351 |
TxD and UL-MIMO requirements for single-port antenna transmission |
Ericsson |
R4-2202352 |
WF on MPR for 26+23 |
Qualcomm |
R4-2202353 |
WF on SRS sharing |
Vivo |
R4-2202354 |
WF on ULFPTx requirements for fallback and SRS antenna switching |
Samsung |
6.7.2.1 |
UL MIMO requirement for TxD except ULFPTx |
|
R4-2200340 |
Draft CR for fixing MPRs in suffix D |
Qualcomm Incorporated |
R4-2201267 |
R17 FR1 TxD requirements and signaling |
OPPO |
R4-2201269 |
Draft R17 CR on UL MIMO falllback to TxD |
OPPO |
6.7.3 |
UE RF requirements for phase 2 (38.101-1) |
|
R4-2201308 |
TxD signalling and inter-band carrier aggregation |
Apple |
6.7.3.1 |
SRS antenna switching related |
|
R4-2200341 |
SRS virtualization for antenna switching |
Qualcomm Incorporated |
R4-2200484 |
Relation of TxD and SRS antenna switching |
Nokia, Nokia Shanghai Bell |
R4-2200859 |
SRS antenna switching with antenna virtualization |
Ericsson |
R4-2200860 |
Pcmax for SRS usage set as antenna switching for TxD and UL-MIMO features |
Ericsson |
R4-2200959 |
Further discussion on SRS antenna switching for TxD |
vivo |
R4-2200960 |
Draft CR on SRS antenna switching for TxD |
vivo |
R4-2201227 |
Discussion on Tx diversity SRS antenna switching |
Xiaomi |
R4-2201271 |
R17 SRS IL for TxD |
OPPO |
R4-2201272 |
Draft R17 CR on SRS IL for TxD |
OPPO |
R4-2201799 |
Further discussion on SRS antenna switching requirements for TxD |
ZTE Wistron Telecom AB |
R4-2201940 |
On SRS relaxation |
Huawei, HiSilicon |
R4-2202350 |
Draft R17 CR on SRS IL for TxD |
OPPO |
6.7.3.2 |
ULFPTx related |
|
R4-2200483 |
Relation of MOP between TxD and ULFPTx |
Nokia, Nokia Shanghai Bell |
R4-2200861 |
Single-antenna falback for TxD and UL-MIMO (including ULFPTx) |
Ericsson |
R4-2200862 |
TxD and UL-MIMO requirements for single-port antenna transmission |
Ericsson |
R4-2200961 |
Discussion on ULFPTx with TxD |
vivo |
R4-2201268 |
R17 FR1 TxD and ULFPTx |
OPPO |
R4-2201762 |
Further Discussion on Transparent TxD – ULFPTx related |
Samsung |
R4-2201798 |
Further discussion on ULFPTx with TxD |
ZTE Wistron Telecom AB |
R4-2201942 |
On ULFPTx and applicable MPR requirements for different PA configurations |
Huawei, HiSilicon |
R4-2202051 |
ULFPTX Mode 2 and TxD |
Qualcomm Incorporated |
6.8.1 |
General |
|
R4-2202554 |
Email discussion summary for [101-bis-e][203] NR_HST_FR1_enh_RRM |
Moderator (CMCC) |
R4-2202720 |
Email discussion summary for [101-bis-e][203] NR_HST_FR1_enh_RRM |
Moderator (CMCC) |
6.8.2 |
RRM core requirements |
|
R4-2200062 |
Discussion on Rel-17 HST in FR1 |
MediaTek (Shenzhen) Inc. |
R4-2200323 |
On NR FR1 HST RRM Requirements |
Qualcomm, Inc. |
R4-2202590 |
WF on RRM requirements for NR FR1 HST |
CMCC |
R4-2202591 |
LS on signalling for inter-frequency measurement enhancement in connected state for FR1 HST |
CMCC |
R4-2202593 |
Draft Big CR on RRM requirements for NR FR1 HST enhancements |
CMCC |
6.8.2.1 |
Intra-frequency measurements |
|
R4-2200626 |
Draft CR on NSCC_SSB for CSSFoutside_gap,i |
CMCC |
6.8.2.2 |
Inter-frequency measurements |
|
R4-2200095 |
Discussion on remaining issues for inter-frequency measurement for FR1 HST |
CATT |
R4-2200635 |
Discussion on NR HST RRM enhancement for inter-frequency measurement |
CMCC |
R4-2200670 |
On R17 FR1 HST inter-frequency measurement |
Apple |
R4-2200876 |
Inter-frequency measurements enhancement for NR HST in FR1 |
Ericsson |
R4-2201172 |
Discussion on inter-frequency measurements for FR1 HST |
Huawei, Hisilicon |
R4-2201173 |
Draft CR on inter-frequency measurements for FR1 HST |
Huawei, Hisilicon |
R4-2202592 |
Draft CR on inter-frequency measurements for FR1 HST |
Huawei, Hisilicon |
6.8.2.3 |
L1-SINR measurements |
|
R4-2200096 |
Discussion on L1-SINR measurements for FR1 HST |
CATT |
R4-2200596 |
Discussion on L1-SINR measurements in R17 FR1 HST |
vivo |
R4-2200671 |
On R17 FR1 HST L1-SINR |
Apple |
R4-2200875 |
L1-SINR measurements requirements enhancement for NR HST in FR1 |
Ericsson |
R4-2201132 |
L1-SINR requirements for Rel17 FR1 HST |
OPPO |
R4-2201582 |
Further discussion on L1-SINR measurements for Rel-17 FR1 HST CA |
Nokia, Nokia Shanghai Bell |
6.8.2.4 |
Others |
|
R4-2200097 |
Discussion on other remaining issues for FR1 HST |
CATT |
R4-2200246 |
On remaining issues for R17 FR1 HST |
Apple |
R4-2200247 |
CR on L1-RSRP measurement in FR1 HST |
Apple |
R4-2200634 |
Discussion on general requirements for FR1 HST RRM |
CMCC |
R4-2200874 |
RRM requirements for NR HST in FR1 |
Ericsson |
R4-2201133 |
Other RRM requirements for Rel17 FR1 HST |
OPPO |
R4-2201174 |
Discussion on remaining issues in FR1 HST |
Huawei, Hisilicon |
6.8.3 |
UE demodulation requirements (38.101-4) |
|
R4-2202963 |
Email discussion summary for [101-bis-e][313] NR_HST_FR1_Demod |
Moderator (CMCC) |
R4-2203105 |
Email discussion summary for [101-bis-e][313] NR_HST_FR1_Demod |
Moderator (CMCC) |
6.8.3.1 |
General |
|
R4-2201422 |
Summary for FR1 HST demodulation results |
Ericsson |
R4-2202981 |
Draft CR on PDSCH requirements for HST-SFN CA requirements for 4Rx |
CMCC |
R4-2202982 |
Draft CR on HST FR1 DPS CA requirements for 2Rx (38.101-4) |
Huawei, HiSilicon |
R4-2202983 |
draft CR: FRC for CA PDSCH demodulation requirements for HST |
Ericsson |
R4-2202984 |
LS on signaling for FR1 HST CA demodulation |
CMCC |
R4-2202985 |
WF on FR1 HST demodulation |
CMCC |
6.8.3.2 |
PDSCH requirements for CA scenarios |
|
R4-2200267 |
Discussion on PDSCH CA Requirements in HST |
Apple |
R4-2200268 |
Draft CR on HST DPS CA requirements for 4Rx |
Apple |
R4-2200364 |
Views on HST CA tests for FR1 |
NTT DOCOMO, INC. |
R4-2200521 |
Discussion on HST FR1 CA PDSCH performance requirements |
Intel Corporation |
R4-2200625 |
Draft CR on PDSCH requirements for HST-SFN CA requirements for 4Rx |
CMCC |
R4-2200633 |
Discussion on FR1 HST UE demodulation for CA scenario |
CMCC |
R4-2200835 |
Discussion on PDSCH requirements for CA scenarios |
ZTE Corporation |
R4-2200998 |
Discussion on PDSCH CA scenarios for NR UE HST FR1 performance requirements |
Huawei,HiSilicon |
R4-2200999 |
Draft CR on HST FR1 DPS CA requirements for 2Rx (38.101-4) |
Huawei,HiSilicon |
R4-2201423 |
PDSCH demodulation requirements for CA with HST-SFN scenario |
Ericsson |
R4-2201424 |
draft CR: FRC for CA PDSCH demodulation requirements for HST |
Ericsson |
R4-2201876 |
draftCR to TS 38.101-4: HST-SFN CA requirements for 2Rx |
Intel Corporation |
R4-2202006 |
Views on FR1 HST PDSCH CA Tests |
Qualcomm Incorporated |
R4-2203123 |
draftCR to TS 38.101-4: HST-SFN CA requirements for 2Rx |
Intel Corporation |
6.9.1 |
General |
|
R4-2201696 |
TR for FR2 HST |
Nokia, Nokia Shanghai Bell, Samsung |
R4-2202272 |
TR for FR2 HST |
Nokia, Nokia Shanghai Bell, Samsung |
6.9.2 |
High speed train deployment scenario in FR2 |
|
R4-2201000 |
TP to TR 38.854 on Deployment Scenario Analysis for FR2 HST |
Huawei,HiSilicon |
R4-2201524 |
TP to TR 38.854: Coverage analysis |
Ericsson |
R4-2203088 |
TP to TR 38.854 on Deployment Scenario Analysis for FR2 HST |
Huawei,HiSilicon |
R4-2203089 |
TP to TR 38.854: Coverage analysis |
Ericsson |
6.9.3 |
UE RF core requirements |
|
R4-2200327 |
On FR2 HST RF Requirements |
Qualcomm, Inc. |
R4-2202223 |
Email discussion summary for [101-bis-e][123] NR_HST_FR2 |
Moderator (Samsung) |
R4-2202323 |
Email discussion summary for [101-bis-e][123] NR_HST_FR2 |
Moderator (Samsung) |
6.9.3.1 |
UE Tx requirements |
|
R4-2201764 |
Draft CR to introduce UE RF requirement for FR2 Power Class 6 |
Samsung |
R4-2202273 |
Draft CR to introduce UE RF requirement for FR2 Power Class 6 |
Samsung |
6.9.3.1.1 |
UE RF framework and power class |
|
R4-2200347 |
UE RF requirement framework for FR2 HST |
Nokia, Nokia Shanghai Bell |
6.9.3.1.2 |
Spherical coverage requirements |
|
R4-2200348 |
UE spherical coverage requirement for FR2 HST |
Nokia, Nokia Shanghai Bell |
R4-2200836 |
Discussion on Spherical coverage requirements for HST_FR2 |
ZTE Corporation |
R4-2201525 |
FR2 HST UE requirements |
Ericsson |
R4-2201763 |
Further Discussion on Spherical Coverage Requirement for FR2 HST UE |
Samsung |
6.9.3.1.3 |
Beam correspondence |
|
R4-2201765 |
Side Conditions for FR2 HST UE Beam Correspondence Requirement |
Samsung |
R4-2202270 |
WF on UE RF requirement for FR2 HST |
Samsung |
R4-2202271 |
Draft TR 38.854 v0.3.0: NR support for high speed train scenario in frequency range 2 (FR2) |
Nokia, Nokia Shanghai Bell, Samsung |
6.9.4 |
RRM core requirements |
|
R4-2200328 |
On NR FR2 HST RRM Requirements |
Qualcomm, Inc. |
6.9.4.1 |
General |
|
R4-2200098 |
Discussion on general issues for FR2 HST |
CATT |
R4-2200259 |
Discussion on general aspects for FR2 HST |
Apple |
R4-2200581 |
General RRM requirements for HST FR2 |
ZTE Corporation |
R4-2200627 |
Discussion on general RRM requirements for FR2 HST |
CMCC |
R4-2200877 |
CR On RRC_CONNECTED state mobility for HST FR2 RRM |
Ericsson |
R4-2200878 |
General requirements for HST FR2 |
Ericsson |
R4-2200883 |
LS on FR2 HST RRM |
Ericsson |
R4-2201156 |
Discussion on general requirements for FR2 HST |
OPPO |
R4-2201175 |
General discussion on network signaling and UE capability in FR2 HST |
Huawei, Hisilicon |
R4-2201666 |
LS on network signalling for Rel-17 FR2 NR HST RRM |
Nokia, Nokia Shanghai Bell |
R4-2201667 |
Discussion on network signalling for FR2 HST RRM |
Nokia, Nokia Shanghai Bell |
R4-2201766 |
Discussion on network signaling and UE capability for FR2 HST |
Samsung |
R4-2201767 |
LS on Network Signalling for Rel-17 NR FR2 HST RRM |
Samsung |
R4-2201847 |
TP to TR 38.854 on Mobility Performance in HST FR2 Deployment Scenarios |
Nokia, Nokia Shanghai Bell |
R4-2202555 |
Email discussion summary for [101-bis-e][204] NR_HST_FR2_RRM_1 |
Moderator (Nokia) |
R4-2202721 |
Email discussion summary for [101-bis-e][204] NR_HST_FR2_RRM_1 |
Moderator (Nokia) |
6.9.4.2 |
Number of RX beams |
|
R4-2200099 |
Discussion on requirements on scenario-B with two-side RRH |
CATT |
R4-2200260 |
Discussion on number of Rx beam for FR2 HST |
Apple |
R4-2200582 |
Discussion on RX beam number for HST FR2 |
ZTE Corporation |
R4-2200881 |
Number of RX beams for HST FR2 |
Ericsson |
R4-2201848 |
TP to TR 38.854 on the Number of Rx beams |
Nokia, Nokia Shanghai Bell |
R4-2202594 |
WF on FR2 HST RRM requirements (part 1) |
Nokia, Nokia Shanghai Bell |
R4-2202595 |
LS on network signaling for Rel-17 NR FR2 HST RRM |
Nokia |
R4-2202596 |
CR On RRC_CONNECTED state mobility for HST FR2 RRM |
Ericsson |
R4-2202765 |
LS on network signaling for Rel-17 NR FR2 HST RRM |
Nokia |
R4-2202766 |
WF on uplink timing for FR2 HST |
Samsung |
R4-2202767 |
WF on uplink timing for FR2 HST |
Samsung |
6.9.4.3 |
RRC Idle/Inactive and connected state mobility requirements |
|
R4-2200100 |
Further discussion on RRC Idle/Inactive and connected state mobility requirements for FR2 HST |
CATT |
R4-2200261 |
Discussion on mobility requirement for FR2 HST |
Apple |
R4-2200583 |
Discussion on RRC Idle Inactive and Connected state mobility requirements for HST FR2 |
ZTE Corporation |
R4-2200628 |
Discussion on mobility requirements for FR2 HST |
CMCC |
R4-2200880 |
RRC Idle/Inactive and connected state mobility requirements for HST FR2 |
Ericsson |
R4-2201176 |
Discussion on RRC Idle/Inactive and connected state mobility requirements for HST in FR2 |
Huawei, Hisilicon |
R4-2201651 |
On RRM measurement requirements for FR2 HST |
Nokia, Nokia Shanghai Bell |
R4-2201652 |
CR to TS 38.133: intra-frequency measurements without gaps for for FR2 NR HST |
Nokia, Nokia Shanghai Bell |
6.9.4.4 |
Timing requirements |
|
R4-2200101 |
Discussion on timing requirement for FR2 HST |
CATT |
R4-2200262 |
Discussion on timing requirement for FR2 HST |
Apple |
R4-2200584 |
Discussion on Timing Requirement for HST FR2 |
ZTE Corporation |
R4-2200882 |
On Timing requirements for HST FR2 |
Ericsson |
R4-2201768 |
Further Discussion on Timing Requirements for FR2 HST |
Samsung |
R4-2201769 |
Draft CR to introduce one shot large UL timing adjustment for FR2 HST UE |
Samsung |
R4-2201846 |
On UL Timing Adjustment in HST FR2 Deployments |
Nokia, Nokia Shanghai Bell |
R4-2202556 |
Email discussion summary for [101-bis-e][205] NR_HST_FR2_RRM_2 |
Moderator (Samsung) |
R4-2202597 |
WF on uplink timing for FR2 HST |
Samsung |
R4-2202599 |
Timing Requirements for FR2 HST |
Samsung |
R4-2202722 |
Email discussion summary for [101-bis-e][205] NR_HST_FR2_RRM_2 |
Moderator (Samsung) |
R4-2202758 |
Draft CR to introduce one shot large UL timing adjustment for FR2 HST UE |
Samsung |
6.9.4.5 |
Signalling characteristics requirements |
|
R4-2200102 |
Discussion on RLM/BFD requirement for FR2 HST |
CATT |
R4-2200104 |
Draft CR on RLM/BFD requirement for FR2 HST |
CATT |
R4-2200263 |
Discussion on signaling characteristic requirement for FR2 HST |
Apple |
R4-2200585 |
Discussion on Signaling characteristics for HST FR2 |
ZTE Corporation |
R4-2200884 |
Signalling characteristics requirements for HST FR2 |
Ericsson |
R4-2201177 |
Discussion on signaling characteristics requirements for high speed train scenario in FR2 |
Huawei, Hisilicon |
R4-2201178 |
Discussion on RRM requirements for high speed train scenario in FR2 |
Huawei, Hisilicon |
R4-2201770 |
Remaining Issues on signaling characteristics requirements for FR2 HST |
Samsung |
R4-2201771 |
Draft CR to introduce active TCI state switching delay requirement for FR2 HST UE |
Samsung |
6.9.4.6 |
Measurement procedure requirements |
|
R4-2200103 |
Further discussion on measurement procedure requirements for FR2 HST |
CATT |
R4-2200264 |
Discussion on measurement procedure requirement for FR2 HST |
Apple |
R4-2200879 |
Measurement procedure requirements for HST FR2 |
Ericsson |
6.9.5 |
Demodulation requirements |
|
R4-2202964 |
Email discussion summary for [101-bis-e][314] NR_HST_FR2_Demod_Part1 |
Moderator (Samsung) |
R4-2203106 |
Email discussion summary for [101-bis-e][314] NR_HST_FR2_Demod_Part1 |
Moderator (Samsung) |
6.9.5.1 |
General |
|
R4-2200743 |
Simulation results summary for Rel-17 FR2 HST |
Samsung |
R4-2200744 |
CR work split for Rel-17 FR2 HST |
Samsung |
R4-2201001 |
Discussion on general UE demodulation requirements for FR2 HST |
Huawei,HiSilicon |
R4-2201002 |
Draft CR on minimum requirements for PDSCH HST-DPS (38.101-4) |
Huawei,HiSilicon |
R4-2201003 |
Draft CR on HST FR2 BS manufacturer's declarations and applicability rule (38.141-2) |
Huawei,HiSilicon |
R4-2203093 |
WF on UE demodulation requirement for FR2 HST |
Samsung |
R4-2203094 |
Simulation assumption for PDSCH requirement for FR2 HST |
Intel Corporation |
6.9.5.2 |
UE demodulation requirements |
|
R4-2200629 |
Discussion on UE demodulation for FR2 HST |
CMCC |
R4-2201718 |
Addressing open issues on FR2 HST UE Demodulation |
Qualcomm Incorporated |
R4-2201877 |
Views on FR2 HST PDSCH performance requirements |
Intel Corporation |
6.9.5.2.1 |
PDSCH requirements under Uni-directional scenario |
|
R4-2200746 |
Discussion and simulation results of PDSCH requirement with Uni-directional scenario for Rel-17 FR2 HST |
Samsung |
R4-2201004 |
Discussion on UE demodulation requirements for FR2 HST under Uni-directional scenario |
Huawei,HiSilicon |
R4-2201425 |
PDSCH demodulation requirements for HST FR2 |
Ericsson |
6.9.5.2.2 |
PDSCH requirements under Bi-directional scenario |
|
R4-2200745 |
Discussion and simulation results of PDSCH requirement with Bi-directional scenario for Rel-17 FR2 HST |
Samsung |
R4-2200837 |
PDSCH requirements under Bi-directional scenario |
ZTE Corporation |
R4-2201005 |
Discussion on UE demodulation requirements for FR2 HST under Bi-directional scenario |
Huawei,HiSilicon |
R4-2201426 |
PDSCH demodulation requirements for HST FR2 bi-directional scenario |
Ericsson |
6.9.5.3 |
BS demodulation requirements |
|
R4-2202965 |
Email discussion summary for [101-bis-e][315] NR_HST_FR2_Demod_Part2 |
Moderator (Nokia) |
R4-2203006 |
WF on BS demodulation requirement for FR2 HST |
Nokia |
R4-2203107 |
Email discussion summary for [101-bis-e][315] NR_HST_FR2_Demod_Part2 |
Moderator (Nokia) |
6.9.5.3.1 |
PUSCH requirements |
|
R4-2200128 |
Discussion on PUSCH demodulation requirements for FR2 HST |
CATT |
R4-2200129 |
Simulation results for PUSCH demodulation requirements for FR2 HST |
CATT |
R4-2200747 |
Discussion and simulation results of PUSCH requirement for Rel-17 FR2 HST |
Samsung |
R4-2201006 |
Discussion on PUSCH demodulation requirements for FR2 HST |
Huawei,HiSilicon |
R4-2201522 |
HST PUSCH requirements |
Ericsson |
R4-2201844 |
On HST FR2 PUSCH Requirements |
Nokia, Nokia Shanghai Bell |
R4-2201878 |
Views on FR2 HST PUSCH performance requirements |
Intel Corporation |
6.9.5.3.2 |
PUSCH with UL timing adjustment requirements |
|
R4-2200130 |
Simulation results for UL timing adjustment demodulation requirements for FR2 HST |
CATT |
R4-2200748 |
Simulation results of UL timing adjustment requirement for Rel-17 FR2 HST |
Samsung |
R4-2201007 |
Discussion on PUSCH with UL timing adjustment requirements for FR2 HST |
Huawei,HiSilicon |
R4-2201523 |
PUSCH with UL timing adjustment requirements |
Ericsson |
R4-2201845 |
On HST FR2 PUSCH UL Timing Adjustment Requirements |
Nokia, Nokia Shanghai Bell |
6.9.5.3.3 |
PRACH requirements |
|
R4-2200131 |
Simulation results for PRACH demodulation requirements for FR2 HST |
CATT |
R4-2200749 |
Simulation results of PRACH requirement for Rel-17 FR2 HST |
Samsung |
R4-2201008 |
Discussion on PRACH demodulation requirements for FR2 HST |
Huawei,HiSilicon |
R4-2201009 |
Draft CR on PRACH minimum requirements for high speed train (38.104) |
Huawei,HiSilicon |
R4-2201010 |
Draft CR on PRACH test requirement for high speed train (38.141-2) |
Huawei,HiSilicon |
R4-2201521 |
FR2 HST PRACH requirement |
Ericsson |
6.10.1 |
General |
|
R4-2202557 |
Email discussion summary for [101-bis-e][206] NR_RRM_enh2_1 |
Moderator (Apple) |
R4-2202598 |
WF on further RRM enhancement for NR and MR-DC – HO with PSCell |
vivo |
R4-2202723 |
Email discussion summary for [101-bis-e][206] NR_RRM_enh2_1 |
Moderator (Apple) |
6.10.2 |
RRM core requirements |
|
R4-2202751 |
Draft Big CR: RRM requirements for Rel-17 NR FeRRM |
Apple |
6.10.2.1 |
SRS antenna port switching |
|
R4-2200068 |
Further discussion on SRS antenna port switching |
CATT |
R4-2200069 |
Interruption requirement to LTE serving cell, and impacts to other LTE RRM requirement |
CATT |
R4-2200179 |
Discussion on SRS antenna port switching |
MediaTek Inc. |
R4-2200288 |
Discussion on SRS antenna port switching |
Apple |
R4-2200322 |
On SRS antenna switching |
Qualcomm, Inc. |
R4-2200531 |
Discussion on SRS antenna port switching |
Intel Corporation |
R4-2200561 |
Discussion on interruption due to SRS antenna port switching |
LG Electronics Inc. |
R4-2200597 |
Discussion on RRM requirements for SRS antenna port switching |
vivo |
R4-2200640 |
Discussion on SRS antenna port switching |
CMCC |
R4-2200684 |
Further discussion on RRM requirements for SRS antenna switching |
Xiaomi |
R4-2200739 |
Discussion on SRS antenna port switching |
ZTE Corporation |
R4-2200895 |
Interruption requirements at SRS antenna port switching |
Nokia, Nokia Shanghai Bell |
R4-2201134 |
RRM requirements for SRS ant port switch |
OPPO |
R4-2201201 |
Discussion on RRM requirements for SRS antenna port switching |
Huawei, Hisilicon |
R4-2201378 |
RRM requirements for SRS antenna port switching |
Ericsson |
R4-2201379 |
Draft CR on Interruption requirement to NR serving cell, and impacts to other NR RRM requirement (if applicable) |
Ericsson |
6.10.2.2 |
HO with PSCell |
|
R4-2200070 |
Further discussion on HO with PSCell |
CATT |
R4-2200289 |
Discussion on RRM requirement for handover with PSCell |
Apple |
R4-2200290 |
Draft CR on HO with PSCell for NR SA to EN-DC_R17 |
Apple |
R4-2200416 |
HO with PSCell |
Qualcomm Incorporated |
R4-2200532 |
Discussion on HO with PSCell |
Intel Corporation |
R4-2200598 |
Discussion on RRM requirements for HO with PSCell |
vivo |
R4-2200630 |
Discussion on HO with PSCell |
CMCC |
R4-2200673 |
Further discussion on RRM requirements for handover with PSCell |
Xiaomi |
R4-2200740 |
Discussion on RRM requirements for HO with PSCell |
ZTE Corporation |
R4-2201135 |
RRM requirements for HO with PSCell |
OPPO |
R4-2201202 |
Discussion on RRM requirements for HO with PSCell |
Huawei, Hisilicon |
R4-2201203 |
Draft CR on requirements for HO with PSCell from EN-DC to EN-DC |
Huawei, Hisilicon |
R4-2201380 |
RRM requirements for handover with PSCell |
Ericsson |
R4-2201381 |
Drfat CR on HO with PSCell requirements for NE DC to NE-DC |
Ericsson |
R4-2201542 |
discussion on HO with PSCell |
Nokia, Nokia Shanghai Bell |
R4-2201543 |
dratCR on HO with PSCell |
Nokia, Nokia Shanghai Bell |
R4-2201851 |
Discussion on HO with PSCell |
MediaTek Inc. |
R4-2202558 |
Email discussion summary for [101-bis-e][207] NR_RRM_enh2_2 |
Moderator (Vivo) |
R4-2202600 |
WF on further RRM enhancement for NR and MR-DC - SRS antenna port switching |
Apple |
R4-2202724 |
Email discussion summary for [101-bis-e][207] NR_RRM_enh2_2 |
Moderator (Vivo) |
R4-2202752 |
Draft CR on requirements for HO with PSCell from EN-DC to EN-DC |
Huawei, Hisilicon |
6.10.2.3 |
PUCCH SCell activation/deactivation |
|
R4-2200071 |
Further discussion on PUCCH SCell activation_deactivation |
CATT |
R4-2200072 |
PUCCH Scell activation delay requirements with multiple Scell |
CATT |
R4-2200180 |
Discussion on PUCCH SCell activation and deactivation |
MediaTek Inc. |
R4-2200181 |
Draft CR for PUCCH SCell deactivation delay requirements in TS 38.133 |
MediaTek Inc. |
R4-2200291 |
Discussion on PUCCH SCell activation and deactivation |
Apple |
R4-2200352 |
Discussions on PUCCH SCell Activation/Deactivation delay requirements |
NTT DOCOMO, INC. |
R4-2200390 |
Remaining issues for PUCCH SCell activation and deactivation |
vivo |
R4-2200418 |
PUCCH SCell activation and deactivation |
Qualcomm Incorporated |
R4-2200533 |
Discussion on PUCCH SCell activation |
Intel Corporation |
R4-2200639 |
Discussion on PUCCH SCell activation/deactivation |
CMCC |
R4-2200674 |
Further discussion on SCell activation and deactication requirements for PUCCH SCell |
Xiaomi |
R4-2200741 |
Discussion on PUCCH SCell activation and deactivation |
ZTE Corporation |
R4-2200893 |
Discussion on the activation delay for deactivated PUCCH SCell |
Nokia, Nokia Shanghai Bell |
R4-2200894 |
38.133 draft CR on PUCCH SCell activation delay requirements |
Nokia, Nokia Shanghai Bell |
R4-2201136 |
RRM requirements for PUCCH SCell Activation/Deactivation |
OPPO |
R4-2201204 |
Discussion on RRM requirements for PUCCH SCell activation |
Huawei, Hisilicon |
R4-2201205 |
Draft CR on interruption of PUCCH SCell activation |
Huawei, Hisilicon |
R4-2201382 |
RRM requirements for SCell activation/deactivation with PUCCH |
Ericsson |
R4-2201383 |
Draft CR on Interruption requirements to LTE serving cell |
Ericsson |
R4-2202559 |
Email discussion summary for [101-bis-e][208] NR_RRM_enh2_3 |
Moderator (CATT) |
R4-2202601 |
WF on further RRM enhancement for NR and MR-DC - PUCCH SCell activation/deactivation requirements |
CATT |
R4-2202602 |
LS on the PL-RS configuration of PUCCH Scell to be activated |
Apple |
R4-2202603 |
WF on R17 NR MG enhancements – multiple concurrent MGs |
MediaTek inc. |
R4-2202604 |
Further reply LS on R17 NR MG enhancements – Concurrent MG |
MediaTek inc. |
R4-2202605 |
CR on CSSF for concurrent gaps |
Apple |
R4-2202725 |
Email discussion summary for [101-bis-e][208] NR_RRM_enh2_3 |
Moderator (CATT) |
R4-2202749 |
Draft CR for PUCCH SCell deactivation delay requirements in TS 38.133 |
MediaTek Inc |
R4-2202768 |
WF on further RRM enhancement for NR and MR-DC - PUCCH SCell activation/deactivation requirements |
CATT |
6.11.1 |
General |
|
R4-2202560 |
Email discussion summary for [101-bis-e][209] NR_MG_enh_1 |
Moderator (MediaTek) |
R4-2202726 |
Email discussion summary for [101-bis-e][209] NR_MG_enh_1 |
Moderator (MediaTek) |
R4-2202753 |
Draft Big CR: RRM requirements Rel-17 NR MG enhancements |
Intel, MediaTek |
6.11.2.1 |
Pre-configured MG pattern(s) |
|
R4-2200110 |
Further discussion on pre-configured MG pattern |
CATT |
R4-2200111 |
Reply LS on R17 NR MG enhancements – Pre-configured MG |
CATT |
R4-2200112 |
Draft CR on measurement delay requirements with Pre-MG |
CATT |
R4-2200240 |
On Pre-MG pattern |
Apple |
R4-2200241 |
CR on Pre-MG activation/deactivation delay |
Apple |
R4-2200387 |
Remaining issues on pre configured MG patterns |
vivo |
R4-2200486 |
Discussion on UE features for measurement gap enhancement |
MediaTek inc. |
R4-2200487 |
Discussion on pre-configured gap |
MediaTek inc. |
R4-2200488 |
Draft CR on 38.133 for L1 measurement impact of preconfigured gap |
MediaTek inc. |
R4-2200537 |
Discussion on pre-configured measurement gap |
Intel Corporation |
R4-2200586 |
Views on pre-configured MG patterns |
ZTE Corporation |
R4-2200595 |
Draft Reply LS to Reply LS onViews on Concurrent MG |
ZTE Corporation |
R4-2200638 |
Discussion on pre-configured MG pattern(s) |
CMCC |
R4-2200675 |
Further discussion on pre-configured MG pattern for NR |
Xiaomi |
R4-2200676 |
DraftCR on inter-RAT measurement delay requirements with pre-configured gaps |
Xiaomi |
R4-2200693 |
DraftCR on inter-frequency measurement requirements with pre-MG in NR |
Intel Corporation |
R4-2200761 |
On pre-configured measurement gaps |
Qualcomm Incorporated |
R4-2201137 |
On pre-configured MG pattern(s) for NR_MG_enh |
OPPO |
R4-2201138 |
Draft CR to 38133 on gap interruption for Pre-MG |
OPPO |
R4-2201621 |
Discussion on pre-configured MG |
Huawei, Hisilicon |
R4-2201622 |
CR on pre-MG applicability |
Huawei, Hisilicon |
R4-2201977 |
Discussion on Pre-configured MG patterns |
Nokia, Nokia Shanghai Bell |
R4-2202009 |
Further analysis of pre-configured measurement gap pattern |
Ericsson |
R4-2202010 |
Measurement requirements for Pre-MG in TS 38.133 |
Ericsson |
R4-2202561 |
Email discussion summary for [101-bis-e][210] NR_MG_enh_2 |
Moderator (Intel) |
R4-2202606 |
Draft CR on inter-RAT measurement requirements with concurrent gaps |
vivo |
R4-2202607 |
Draft CR on 38.133 for L1 measurement impact of concurrent gaps |
MediaTek inc. |
R4-2202608 |
DraftCR on inter-frequency measurement delay requirements with concurrent gaps |
Xiaomi |
R4-2202609 |
DraftCR on positioning measurement requirements due to concurrent gap in NR |
Intel Corporation |
R4-2202610 |
Draft CR to 38133 on CSI-RS based L3 measurement requirements with concurrent gap |
OPPO |
R4-2202611 |
draftCR on concurrent gaps (9.1.2B) |
Ericsson |
R4-2202612 |
CR on collision handling and MG related requirements for concurrent MGs |
Huawei, Hisilicon |
R4-2202613 |
Draft CR on measurement delay requirements for concurrent MG patterns |
CATT |
R4-2202614 |
WF on R17 NR MG enhancements – Pre-configured MG |
Intel |
R4-2202615 |
LS on R17 NR MG enhancements – Pre-configured MG |
Intel |
R4-2202616 |
Reply LS on R17 NR MG enhancements – Pre-configured MG |
CATT |
R4-2202617 |
Draft CR on measurement delay requirements with Pre-MG |
CATT |
R4-2202618 |
CR on Pre-MG activation/deactivation delay |
Apple |
R4-2202619 |
Draft CR on 38.133 for L1 measurement impact of preconfigured gap |
MediaTek |
R4-2202620 |
DraftCR on inter-RAT measurement delay requirements with pre-configured gaps |
Xiaomi |
R4-2202621 |
DraftCR on inter-frequency measurement requirements with pre-MG in NR |
Intel |
R4-2202622 |
Draft CR to 38133 on gap interruption for Pre-MG |
Oppo |
R4-2202623 |
CR on pre-MG applicability |
Huawei |
R4-2202624 |
Measurement requirements for Pre-MG in TS 38.133 |
Ericsson |
R4-2202727 |
Email discussion summary for [101-bis-e][210] NR_MG_enh_2 |
Moderator (Intel) |
6.11.2.2 |
Multiple concurrent and independent MG patterns |
|
R4-2200113 |
Further discussion on multiple concurrent and independent MG patterns |
CATT |
R4-2200114 |
Reply LS on R17 NR MG enhancements – Concurrent MG |
CATT |
R4-2200115 |
Draft CR on measurement delay requirements for concurrent MG patterns |
CATT |
R4-2200242 |
On multiple concurrent and independent MG patterns |
Apple |
R4-2200243 |
CR on CSSF for concurrent gaps |
Apple |
R4-2200388 |
Remaining issues on multiple concurrent and independent MG patterns |
vivo |
R4-2200404 |
Draft CR on inter-RAT measurement requirements with concurrent gaps |
vivo |
R4-2200489 |
Discussion on concurrent gaps |
MediaTek inc. |
R4-2200490 |
Draft CR on 38.133 for L1 measurement impact of concurrent gaps |
MediaTek inc. |
R4-2200538 |
Discussion on multiple and independent concurrent measurement gaps in NR |
Intel Corporation |
R4-2200560 |
Discussion on multiple concurrent and independent MG patterns |
LG Electronics |
R4-2200587 |
Views on multiple concurrent and independent MGs |
ZTE Corporation |
R4-2200631 |
Discussion on multiple concurrent and independent MG patterns |
CMCC |
R4-2200677 |
Further discussion on multiple concurrent and independent MG patterns for NR |
Xiaomi |
R4-2200678 |
DraftCR on inter-frequency measurement delay requirements with concurrent gaps |
Xiaomi |
R4-2200694 |
DraftCR on positioning measurement requirements due to concurrent gap in NR |
Intel Corporation |
R4-2200762 |
On multiple concurrent measurement gaps |
Qualcomm Incorporated |
R4-2201139 |
On multiple concurrent and independent MG patterns for NR_MG_enh |
OPPO |
R4-2201140 |
Draft CR to 38133 on CSI-RS based L3 measurement requirements with concurrent gap |
OPPO |
R4-2201213 |
Discussion on multiple concurrent MG patterns |
Ericsson |
R4-2201214 |
draftCR on concurrent gaps (9.1.2B) |
Ericsson |
R4-2201623 |
Discussion on multiple concurrent MGs |
Huawei, Hisilicon |
R4-2201624 |
CR on collision handling and MG related requirements for concurrent MGs |
Huawei, Hisilicon |
R4-2201694 |
Discussion on concurrent measurement gap enhancements |
Nokia, Nokia Shanghai Bell |
R4-2201695 |
Discussion on LS on R17 NR Concurrent MG enhancements |
Nokia, Nokia Shanghai Bell |
6.11.2.3 |
Network Controlled Small Gap |
|
R4-2200116 |
Further discussion on Network Controlled Small Gap (NCSG) |
CATT |
R4-2200117 |
Draft CR on measurement delay requirements with NCSG |
CATT |
R4-2200244 |
On network controlled small gap |
Apple |
R4-2200245 |
CR on NCSG applicability |
Apple |
R4-2200329 |
On NCSG requirement |
Qualcomm, Inc. |
R4-2200389 |
Remaining issues for NCSG |
vivo |
R4-2200405 |
Draft CR for interruption for de-activated SCell measurement due to NCSG |
vivo |
R4-2200491 |
Discussion on NCSG |
MediaTek inc. |
R4-2200492 |
Draft CR on 38.133 for L1 measurement impact of NCSG |
MediaTek inc. |
R4-2200539 |
Discussion on NCSG in NR |
Intel Corporation |
R4-2200588 |
Views on NCSG |
ZTE Corporation |
R4-2200632 |
Further discussion on Network Controlled Small Gap |
CMCC |
R4-2200695 |
DraftCR on interruption of NCSG in NR |
Intel Corporation |
R4-2201157 |
Draft CR to UE behaviour to group the frequency layers with NCSG |
OPPO |
R4-2201158 |
Discussion on NCSG for NR_MG_enh |
OPPO |
R4-2201232 |
Draft CR for UE behavior after the interruptions of NCSG |
ZTE Corporation |
R4-2201625 |
Discussion on NCSG |
Huawei, Hisilicon |
R4-2201626 |
CR on use cases and CSSF for NCSG |
Huawei, Hisilicon |
R4-2201976 |
CR: NCSG scheduling restriction |
Qualcomm communications-France |
R4-2201978 |
Discussion on Network Controlled Small Gaps for NR |
Nokia, Nokia Shanghai Bell |
R4-2202011 |
Further analysis of network controlled small gap |
Ericsson |
R4-2202012 |
Measurement requirements for NCSG in TS 38.133 |
Ericsson |
R4-2202562 |
Email discussion summary for [101-bis-e][211] NR_MG_enh_3 |
Moderator (Apple) |
R4-2202625 |
WF on R17 NR MG enhancements – NCSG |
Apple |
R4-2202626 |
LS on R17 MG enhancement - NCSG |
Apple |
R4-2202627 |
Draft CR on measurement delay requirements with NCSG |
CATT |
R4-2202628 |
CR on NCSG applicability |
Apple |
R4-2202629 |
Draft CR for interruption for de-activated SCell measurement due to NCSG |
vivo |
R4-2202630 |
Draft CR on 38.133 for L1 measurement impact of NCSG |
MediaTek inc. |
R4-2202631 |
DraftCR on interruption of NCSG in NR |
Intel Corporation |
R4-2202632 |
Draft CR to UE behaviour to group the frequency layers with NCSG |
OPPO |
R4-2202633 |
Draft CR for UE behavior after the interruptions of NCSG |
ZTE Corporation |
R4-2202634 |
CR on use cases and CSSF for NCSG |
Huawei, Hisilicon |
R4-2202635 |
CR: NCSG scheduling restriction |
Qualcomm communications-France |
R4-2202636 |
Measurement requirements for NCSG in TS 38.133 |
Ericsson |
R4-2202728 |
Email discussion summary for [101-bis-e][211] NR_MG_enh_3 |
Moderator (Apple) |
6.12.1 |
General |
|
R4-2200017 |
Draft TR 38.833 v1.1.0: Further enhancement on NR demodulation performance |
China Telecom |
R4-2200018 |
TP to TR 38.833: Symbols and abbreviations |
China Telecom |
R4-2200905 |
Updated work plan for Further enhancement on NR demodulation performance WI |
China Telecom |
R4-2201603 |
Discussion on UE feature list and capability signalling for NR Demodulation Enhancements WI |
Intel Corporation |
R4-2202966 |
Email discussion summary for [101-bis-e][316] NR_perf_enh2_Demod_Part1 |
Moderator (China Telecom) |
R4-2203008 |
WF on general and PDSCH demodulation requirements for inter-cell interference MMSE-IRC |
Intel |
R4-2203009 |
WF on CSI requirements for inter-cell interference MMSE-IRC |
Ericsson |
R4-2203010 |
Summary of simulation results for Inter-cell MMSE-IRC CQI reporting |
Ericsson |
R4-2203011 |
WF on MMSE-IRC receiver for intra-cell inter-user interference |
Huawei |
R4-2203028 |
WF on general part and 15kHz NR SCS scenario for CRS-IM receiver |
Chinal Telecom |
R4-2203029 |
WF on 30 kHz NR SCS scenario for CRS-IM receiver |
CMCC |
R4-2203108 |
Email discussion summary for [101-bis-e][316] NR_perf_enh2_Demod_Part1 |
Moderator (China Telecom) |
R4-2203131 |
WF on general part and 15kHz NR SCS scenario for CRS-IM receiver |
China Telecom |
6.12.2 |
UE demodulation and CSI requirements |
|
R4-2203007 |
TP to TR 38.833: Link level simulation results for Inter-user interference suppression for MU-MIMO |
Intel |
6.12.2.1 |
MMSE-IRC receiver for inter-cell interference |
|
R4-2202967 |
Email discussion summary for [101-bis-e][317] NR_perf_enh2_Demod_Part2 |
Moderator (Intel) |
R4-2203109 |
Email discussion summary for [101-bis-e][317] NR_perf_enh2_Demod_Part2 |
Moderator (Intel) |
6.12.2.1.1 |
PDSCH requirements |
|
R4-2200269 |
Discussion on PDSCH requirements in intercell interference scenarios |
Apple |
R4-2200270 |
Draft CR on PDSCH demod requirements in ICI-FDD |
Apple |
R4-2200366 |
Views on MMSE-IRC receiver for inter-cell interference test |
NTT DOCOMO, INC. |
R4-2200377 |
Discussion on the PDSCH requirements for scenarios with inter-cell inter-user interference |
MediaTek inc. |
R4-2200500 |
On Intercell PDSCH MMSE-IRC demodulation requirements |
Nokia, Nokia Shanghai Bell |
R4-2200504 |
TP for 38.101-4 on NR Interference model for enhanced performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2200512 |
Discussion on PDSCH demodulation MMSE-IRC requirements for scenario with inter-cell interference |
Intel Corporation |
R4-2200513 |
Summary of PDSCH simulation results for inter-cell interference suppression |
Intel Corporation |
R4-2200795 |
Draft CR for TS38.101-4 PDSCH TDD demodulation requirements for inter-cell interference MMSE-IRC |
CMCC |
R4-2200798 |
Discussion on R17 demodulation enhancement for inter-cell interference suppressing |
CMCC |
R4-2200902 |
On PDSCH requirements for UE MMSE-IRC receiver for inter-cell interference suppression |
China Telecom |
R4-2200985 |
Discussion on Inter cell IRC demodulation requirements |
Huawei,HiSilicon |
R4-2200986 |
Simulation results for Inter cell IRC demodulation requirements |
Huawei,HiSilicon |
R4-2200988 |
Draft CR: Introduction of general and applicability section of inter-cell MMSE-IRC receiver in TS 38.101-4 |
Huawei,HiSilicon |
R4-2201215 |
Remaining issues on PDSCH requirement for inter-cell interference |
Ericsson |
R4-2201216 |
Simulation results on PDSCH performance for inter-cell interference |
Ericsson |
R4-2201965 |
Views on Inter-cell Interference PDSCH Tests |
Qualcomm Incorporated |
6.12.2.1.2 |
CQI requirements |
|
R4-2200271 |
Discussion on CSI reporting requirements in intercell interference scenarios |
Apple |
R4-2200378 |
Discussion on the CQI requirements for scenarios with inter-cell inter-user interference |
MediaTek inc. |
R4-2200501 |
On CQI requirements for intercell interference MMSE-IRC |
Nokia, Nokia Shanghai Bell |
R4-2200514 |
Discussion on CSI MMSE-IRC requirements for scenario with inter-cell interference |
Intel Corporation |
R4-2200799 |
Discussion on CQI requirements for inter-cell interference MMSE-IRC |
CMCC |
R4-2200901 |
On CSI requirements for UE MMSE-IRC receiver for inter-cell interference suppression |
China Telecom |
R4-2200987 |
Discussion and simulations results for Inter cell IRC CSI |
Huawei,HiSilicon |
R4-2201217 |
Remaining issues on CSI reporting requirements for inter-cell interference |
Ericsson |
R4-2201218 |
Simulation results on CSI reporting for inter-cell interference |
Ericsson |
R4-2201221 |
draftCR on CSI reporting test case(TDD) |
Ericsson |
R4-2201975 |
Views on Inter-cell Interference CQI Reporting Tests |
Qualcomm Incorporated |
6.12.2.2 |
MMSE-IRC receiver for intra-cell inter-user interference |
|
R4-2200272 |
Discussion on PDSCH requirements in MU-MIMO scenarios |
Apple |
R4-2200379 |
Discussion on the PDSCH requirements for scenarios with intra-cell inter-user interference |
MediaTek inc. |
R4-2200380 |
TP to TR 38.833 Scenario for inter-user interference suppression for MU-MIMO |
MediaTek inc. |
R4-2200515 |
Discussion on MMSE-IRC requirements for scenario with intra-cell inter-user interference |
Intel Corporation |
R4-2200516 |
TP to TR 38.833: Link level simulation results for Inter-user interference suppression for MU-MIMO |
Intel Corporation |
R4-2200800 |
Discussion on R17 demodulation enhancement for intra-cell inter-user interference suppressing |
CMCC |
R4-2200807 |
TP to TR 38.833: Summary of link level evaluation for inter-user interference suppression for MU-MIMO |
CMCC |
R4-2200903 |
Views on UE MMSE-IRC receiver for intra-cell inter-user interference suppression |
China Telecom |
R4-2200904 |
TP to TR 38.833: Updated conclusion for phase I evaluation on inter-user interference suppression for MU-MIMO scenario |
China Telecom |
R4-2200989 |
TP to TR 38.833: Introduction of simulation assumptions of intra cell inter user MMSE-IRC receiver |
Huawei,HiSilicon |
R4-2200990 |
Discussions on intra-cell inter user MMSE-IRC receiver |
Huawei,HiSilicon |
R4-2200991 |
Simulation results for intra cell inter user MMSE IRC receiver |
Huawei,HiSilicon |
R4-2200992 |
Draft CR: Introduction of MU-MIMO Beamforming model in TS 38.101-4 |
Huawei,HiSilicon |
R4-2200993 |
Summary of simulation results for intra cell inter user MMSE receiver requirements |
Huawei,HiSilicon |
R4-2201219 |
Remaining issues on MMSE-IRC receiver for intra-cell inter-user interference |
Ericsson |
R4-2201220 |
Simulation results on PDSCH performance for intra-cell inter-user interference |
Ericsson |
R4-2201966 |
Views on Intra-cell Inter-user Interference Scenarios |
Qualcomm Incorporated |
6.12.2.3 |
CRS-IM receiver in scenarios with overlapping spectrum for LTE and NR |
|
R4-2201964 |
Views on CRS Interference Mitigation in NR |
Qualcomm Incorporated |
6.12.2.3.1 |
General |
|
R4-2200273 |
Discussion on CRS-IM with 30KHz SCS |
Apple |
R4-2200502 |
On Receiver Assumptions for CRS-IM |
Nokia, Nokia Shanghai Bell |
R4-2200517 |
General discussion on CRS-IM requirements for scenarios with overlapping spectrum for LTE and NR |
Intel Corporation |
R4-2200801 |
Discussion on the receiver for CRS-IM |
CMCC |
R4-2200898 |
Discussion on the receiver assumption for CRS-IM requirement definition |
China Telecom |
R4-2200982 |
Discussion on CRS-IM receiver for 30kHz SCS |
Huawei,HiSilicon |
R4-2201414 |
CRS-IM receiver in scenarios with overlapping spectrum for LTE and NR |
ZTE Corporation |
R4-2201415 |
Simulation results on CRS-IM receiver |
ZTE Corporation |
R4-2201418 |
Discussion on remaining issues of receiver assumption for CRS-IM |
Ericsson |
6.12.2.3.2 |
Necessity of Network assistant signaling |
|
R4-2200274 |
Discussion on Network Assistance for CRS-IM in NR |
Apple |
R4-2200381 |
Views on the network assistance signalling for CRS-IM receiver |
MediaTek inc. |
R4-2200503 |
On Necessity of Network assistant signaling for CRS-IM |
Nokia, Nokia Shanghai Bell |
R4-2200518 |
Network assistant signaling for CRS-IM receiver for scenarios with overlapping spectrum for LTE and NR |
Intel Corporation |
R4-2200802 |
Discussion on the network assistant signaling necessity for CRS-IM |
CMCC |
R4-2200899 |
Discussion on the necessity of network assistance signalling for CRS-IM |
China Telecom |
R4-2200984 |
Discussion on necessity of NWA on CRS-IM receiver for 15kHz SCS |
Huawei,HiSilicon |
R4-2201416 |
Discussion on the network assistance signalling for CRS-IM |
Ericsson |
R4-2201417 |
Simulation results for CRS interference handling |
Ericsson |
6.12.2.3.3 |
Test set-up |
|
R4-2200275 |
Discussion on Test setup for CRS-IM requirements |
Apple |
R4-2200519 |
Test setup for CRS-IM receiver for scenarios with overlapping spectrum for LTE and NR |
Intel Corporation |
R4-2200803 |
Discussion on the test setup for CRS-IM |
CMCC |
R4-2200900 |
Discussion on the test setup for CRS-IM requirement definition |
China Telecom |
R4-2200983 |
Discussion on test setup on CRS-IM receiver for 15kHz SCS |
Huawei,HiSilicon |
R4-2201419 |
Discussion on the remaining issues of test setup for CRS-IM |
Ericsson |
R4-2201601 |
On test setup for CRS-IM |
Nokia, Nokia Shanghai Bell |
6.12.3 |
BS demodulation requirements |
|
R4-2202968 |
Email discussion summary for [101-bis-e][318] NR_perf_enh2_Demod_Part3 |
Moderator (Huawei) |
R4-2203110 |
Email discussion summary for [101-bis-e][318] NR_perf_enh2_Demod_Part3 |
Moderator (Huawei) |
6.12.3.1 |
PUSCH demodulation requirements for FR1 256QAM |
|
R4-2200132 |
Draft CR for TS 38.141-1 on manufacture declaration for FR1 PUSCH 256QAM performance requirements |
CATT |
R4-2200133 |
Simulation results for FR1 PUSCH 256QAM performance requirement |
CATT |
R4-2200148 |
Draft CR for TS 38.141-2, Introduction of manufacture declaration, MU and TT for FR1 PUSCH 256QAM performance requirements |
CATT |
R4-2200474 |
draftCR for 38.141-1 MU and TT for PUSCH with 256QAM |
Ericsson |
R4-2200520 |
Draft CR for TS 38.104: FR1 256QAM PUSCH requirements |
Intel Corporation |
R4-2200752 |
draft CR on FR1 PUSCH 256QAM FRC for TS 38.104 |
Samsung |
R4-2200753 |
draft CR on FR1 PUSCH 256QAM FRC for TS 38.141-1 |
Samsung |
R4-2200754 |
draft CR on FR1 PUSCH 256QAM FRC for TS 38.141-2 |
Samsung |
R4-2200755 |
Simulation results for FR1 PUSCH with 256QAM |
Samsung |
R4-2200796 |
Draft CR for TS38.141-2 Requirements for PUSCH with transform precoding disabled for BS type 1-O |
CMCC |
R4-2200838 |
Simulation results for FR1 UL 256QAM demodulation requirement |
ZTE Corporation |
R4-2201018 |
Updated simulation results for FR1 PUSCH 256QAM performance requirements |
Huawei,HiSilicon |
R4-2201019 |
Summary of simulation results for FR1 PUSCH 256QAM performance requirements |
Huawei,HiSilicon |
R4-2201020 |
draftCR: Introduction of conformance testing for FR1 PUSCH 256QAM with transform precoding disabled in TS 38.141-1 |
Huawei,HiSilicon |
R4-2201801 |
Simulation results for FR1 UL 256QAM demodulation requirement |
ZTE Wistron Telecom AB |
R4-2201802 |
draftCR on FR1 PUSCH 256QAM FRC for TS 38.104 |
ZTE Wistron Telecom AB |
R4-2203001 |
Draft CR for TS 38.141-2, Introduction of manufacture declaration, MU and TT for FR1 PUSCH 256QAM performance requirements |
CATT |
R4-2203002 |
Draft CR for TS 38.104: FR1 256QAM PUSCH requirements |
Intel |
R4-2203003 |
Draft CR for TS38.141-2 Requirements for PUSCH with transform precoding disabled for BS type 1-O |
CMCC |
R4-2203004 |
draftCR: Introduction of conformance testing for FR1 PUSCH 256QAM with transform precoding disabled in TS 38.141-1 |
Huawei,HiSilicon |
R4-2203005 |
WF for FR1 PUSCH with 256QAM performance requirements |
Huawei |
6.13.1 |
General |
|
R4-2201170 |
Draft text proposal to update TR 38.863 |
Samsung |
R4-2201991 |
Considerations for TS 38.101-5 development |
MediaTek (Chengdu) Inc. |
R4-2202969 |
Email discussion summary for [101-bis-e][306] NTN_Solutions_Part1 |
Moderator (THALES) |
R4-2203080 |
Way Forward on NTN_solutions_Part1 |
THALES |
R4-2203081 |
Draft text proposal to update TR 38.863 |
Samsung |
R4-2203086 |
Draft skeleton for TS 38.101-5 |
Samsung |
R4-2203087 |
Skeleton for TS 38.108 NR Satellite Access Node radio transmission and reception v0.0.1 |
THALES |
R4-2203111 |
Email discussion summary for [101-bis-e][306] NTN_Solutions_Part1 |
Moderator (THALES) |
R4-2203132 |
Draft TR 38.863 update v0.2.0 |
Samsung |
6.13.1.1 |
System parameters |
|
R4-2200162 |
On remaining open issue for NTN system parameters |
CATT |
R4-2200163 |
TP to TR 38.863 on channel raster and sync raster |
CATT |
R4-2200478 |
TP to TR 38.863 on operating bands and channel bandwidth |
CATT |
R4-2200479 |
TP to TR 38.863 on transmitter characteristics for satellite access node |
CATT |
R4-2201074 |
On NTN System parameters |
Nokia, Nokia Shanghai Bell |
R4-2201257 |
TP for 38.863 on system parameters to clarify “NTN satellite bands” |
Huawei, HiSilicon |
R4-2201989 |
NTN system parameters remaining issues for n255 |
MediaTek (Chengdu) Inc. |
R4-2203082 |
TP to TR 38.863 on channel raster and sync raster |
CATT |
R4-2203083 |
NTN - Regulatory information - TP to TR 38.863 |
Ericsson |
R4-2203084 |
TP to TR 38.863 on regulatory aspects for HAPS |
Nokia, Nokia Shanghai Bell |
R4-2203085 |
TP to TR 38.863 on general aspects |
Nokia, Nokia Shanghai Bell |
6.13.1.2 |
NTN Satellite Access Node Class/Type |
|
R4-2200165 |
Satellite Access Node Class/Type |
CATT |
R4-2201465 |
Further discussion on NTN gNB class |
ZTE Corporation |
6.13.1.3 |
Regulatory information |
|
R4-2201075 |
TP to TR 38.863 on regulatory aspects for HAPS |
Nokia, Nokia Shanghai Bell |
R4-2201314 |
NTN - Regulatory information - TP to TR 38.863 |
Ericsson |
R4-2203129 |
NTN - Regulatory information - TP to TR 38.863 |
Ericsson |
6.13.1.4 |
Others |
|
R4-2200363 |
Considerations on HAPS specific technical requirements |
SoftBank Corp., KDDI Corporation, Intelsat |
R4-2201076 |
TP to TR 38.863 on general aspects |
Nokia, Nokia Shanghai Bell |
R4-2201263 |
Draft skeleton for TS 38.101-5 |
Samsung |
R4-2201288 |
Draft skeleton for TS 38.101-5 |
Samsung |
R4-2201315 |
NTN - General aspects related to BS and UE requirements |
Ericsson |
R4-2201830 |
Skeleton for TS 38.108 NR Satellite Access Node radio transmission and reception v0.0.1 |
THALES |
R4-2201838 |
Draft proposal to update TR 38.863 NTN related RF and co-existence aspects |
THALES |
6.13.2 |
Coexistence aspects |
|
R4-2202970 |
Email discussion summary for [101-bis-e][307] NTN_Solutions_Part2 |
Moderator (Samsung) |
R4-2202988 |
Draft Text Proposal for TR 38.863 Chapter 6.3 and 6.4 |
Samsung |
R4-2202990 |
WF on [307] NTN_Solutions_Part2 |
Samsun |
R4-2202991 |
Simulation assumptions for NTN co-existence |
Samsung, CATT |
R4-2202992 |
Simulation assumptions for HAPS co-existence |
Nokia |
R4-2202993 |
Summary of NTN co-existence study |
Samsung |
R4-2202994 |
Summary of HAPS co-existence study |
Nokia |
R4-2203112 |
Email discussion summary for [101-bis-e][307] NTN_Solutions_Part2 |
Moderator (Samsung) |
R4-2203130 |
WF on [307] NTN_Solutions_Part2 |
Samsung |
6.13.2.1 |
NTN coexistence scenarios and simulations |
|
R4-2200164 |
NTN coexistence simulations |
CATT |
R4-2200781 |
Coexistence simulation results for TN-NTN |
Qualcomm Incorporated |
R4-2201072 |
NR-NTN co-ex study results |
Samsung |
R4-2201124 |
Collected NR-NTN co-ex results |
Samsung |
R4-2201222 |
Simulation result for coexistence study on NR to support non-terrestrial networks |
Xiaomi |
R4-2201255 |
NR NTN co-existence simulation Results |
Huawei, HiSilicon |
R4-2201262 |
NTN coexistence results and observations |
MediaTek (Chengdu) Inc. |
R4-2201316 |
NTN - Coexistence simulation results |
Ericsson |
R4-2201466 |
Simulation results for NTN coexistence study |
ZTE Corporation |
R4-2201842 |
NTN Simulation Assumptions |
THALES |
R4-2201843 |
NTN coexistence calibration data - THALES 28_09_2021 |
THALES |
R4-2201852 |
NR-NTN coexistence results - THALES updates 10_01_2022 |
THALES |
6.13.2.2 |
HAPS coexistence scenarios and simulations |
|
R4-2200782 |
Coexistence simulation restuls for HAPS |
Qualcomm Incorporated |
R4-2201077 |
HAPS simulation assumptions for coexistence study |
Nokia, Nokia Shanghai Bell |
R4-2201078 |
TP to TR 38.863 on HAPS coexistence study |
Nokia, Nokia Shanghai Bell |
R4-2201254 |
Discussion on HAPS requirements |
Huawei, HiSilicon |
6.13.2.3 |
ACLR/ACS proposals |
|
R4-2200166 |
ACLR/ACS proposal |
CATT |
R4-2201079 |
ACLR and ACS proposal for HAPS |
Nokia, Nokia Shanghai Bell |
R4-2201126 |
NR-NTN co-ex results analysis and ACLR ACS proposal |
Samsung |
R4-2201127 |
Draft Text Proposal for TR 38.863 Chapter 6.3 and 6.4 |
Samsung |
R4-2201256 |
Discussion on ACLR and ACS for NR NTN |
Huawei, HiSilicon |
R4-2201317 |
NTN - ACLR/ACS proposals |
Ericsson |
R4-2201467 |
Discussion on ACLR and ACS requirements for NTN |
ZTE Corporation |
R4-2201839 |
TN-NTN Coexistence Results Updates |
THALES, Magister Solutions Ltd |
6.13.3 |
Satellite Access Node RF requirements |
|
R4-2200167 |
Remaining issue for satellite access node RF requirement - Tx part |
CATT |
R4-2200168 |
Remaining issue for satellite access node RF requirement - Rx part |
CATT |
R4-2202971 |
Email discussion summary for [101-bis-e][308] NTN_Solutions_Part3 |
Moderator (Huawei) |
R4-2203033 |
WF on BS RF requirements for SAN type 1-H |
CATT |
R4-2203034 |
WF on Tx RF requirement for SAN type 1-O |
ZTE |
R4-2203035 |
WF on Rx RF requirement for SAN type 1-O |
Ericsson |
R4-2203036 |
WF on UE RF requirement for NTN UE |
Huawei |
R4-2203037 |
TP for 38.863 on UE transmission characteristics for satellite access |
Huawei |
R4-2203038 |
TP for 38.863 on maximum input level for NTN UE |
Xiaomi |
R4-2203039 |
TP for 38.863 on UE Receiver characteristics for satellite access |
Huawei |
R4-2203040 |
TP to TR 38.863 on transmitter characteristics for satellite access node |
CATT |
R4-2203113 |
Email discussion summary for [101-bis-e][308] NTN_Solutions_Part3 |
Moderator (Huawei) |
R4-2203124 |
WF on BS RF requirements for SAN type 1-H |
CATT |
6.13.3.1 |
TX requirements for radiated characteristics |
|
R4-2200169 |
Discussion on NTN BS RF requriement for type 1-O - Tx part |
CATT |
R4-2201258 |
Discussion on UE Tx requirements for satellite access |
Huawei, HiSilicon |
R4-2201260 |
TP for 38.863 on UE transmitter characteristics for satellite access |
Huawei, HiSilicon |
R4-2201318 |
NTN - Satellite Node Access - Tx requirements |
Ericsson |
R4-2201468 |
Discussion on radiated Tx requirements of satellite access node |
ZTE Corporation |
R4-2201816 |
Discussion on Satellite Access Node radiated RF requirements: Tx |
Huawei |
R4-2202406 |
UE Array, EIRP level and Spherical Coverage at 60 GHz |
Sony, Ericsson |
6.13.3.2 |
RX requirements for radiated characteristics |
|
R4-2200170 |
Discussion on NTN BS RF reqruiement for type 1-O - Rx part |
CATT |
R4-2201259 |
Discussion on UE Rx requirements for satellite access |
Huawei, HiSilicon |
R4-2201261 |
TP for 38.863 on UE Receiver characteristics for satellite access |
Huawei, HiSilicon |
R4-2201319 |
NTN - Satellite Node Access - Rx requirements |
Ericsson |
R4-2201469 |
Discussion on radiated Rx requirements of satellite access node |
ZTE Corporation |
R4-2201817 |
Discussion on Satellite Access Node radiated RF requirements: Rx |
Huawei |
6.13.3.3 |
Tx requirements for conducted characteristics |
|
R4-2201320 |
NTN - Satellite Node Access - OTA Tx requirements |
Ericsson |
R4-2201470 |
Discussion on conducted Tx requirements of satellite access node |
ZTE Corporation |
R4-2201818 |
Discussion on Satellite Access Node conducted RF requirements: Tx |
Huawei |
R4-2201819 |
Discussion on 64QAM support for the Satellite Access Node operation in FR1 |
Huawei, HiSilicon |
6.13.3.4 |
Rx requirements for conducted characteristics |
|
R4-2201321 |
NTN - Satellite Node Access - OTA Rx requirements |
Ericsson |
R4-2201471 |
Discussion on conducted RF requirements from satellite network perspective |
ZTE Corporation |
R4-2201820 |
Discussion on Satellite Access Node conducted RF requirements: Rx |
Huawei |
6.13.4.1 |
TX requirements |
|
R4-2200073 |
Further discussion on UE Tx RF requirements for NTN |
CATT |
R4-2200331 |
Discussion on UE TX requirements for NTN |
Mediatek India Technology Pvt. |
R4-2200783 |
Considerations on NTN UE Tx requirements |
Qualcomm Incorporated |
R4-2201310 |
Discussion on UE Tx requirements for satellite access |
Huawei, HiSilicon |
R4-2201312 |
TP for 38.863 on UE transmitter characteristics for satellite access |
Huawei, HiSilicon |
R4-2201322 |
NTN - UE - Tx requirements |
Ericsson |
R4-2201472 |
Discussion on NTN UE Tx RF requirements |
ZTE Corporation |
6.13.4.2 |
RX requirements |
|
R4-2200074 |
Further discussion on UE Rx RF requirements for NTN |
CATT |
R4-2200332 |
Discussion on UE RX requirements for NTN |
Mediatek India Technology Pvt. |
R4-2200784 |
Considerations on NTN UE Rx requirements |
Qualcomm Incorporated |
R4-2201223 |
TP for 38.863 on maximum input power for NTN UE |
Xiaomi |
R4-2201224 |
Discussion on Maximum input level for NTN UE |
Xiaomi |
R4-2201311 |
Discussion on UE Rx requirements for satellite access |
Huawei, HiSilicon |
R4-2201313 |
TP for 38.863 on UE Receiver characteristics for satellite access |
Huawei, HiSilicon |
R4-2201323 |
NTN - UE - Rx requirements |
Ericsson |
R4-2201473 |
Discussion on NTN UE Rx RF requirements |
ZTE Corporation |
6.13.5.1 |
General |
|
R4-2200075 |
Further discussion on RRM requirements for NTN |
CATT |
R4-2200419 |
General and RRM requirements impacts |
Qualcomm Incorporated |
R4-2200564 |
Discussion on NTN general requirements |
LG Electronics Inc. |
R4-2200737 |
Discussion on General RRM Requirements for NTN UE |
ZTE Corporation |
R4-2200890 |
General requirements for NTN |
Ericsson |
R4-2200930 |
Discussion on general RRM requirements in NTN |
MediaTek inc. |
R4-2201141 |
Discussion on general RRM requirements for NTN |
OPPO |
R4-2201520 |
On the SMTC windows |
Nokia, Nokia Shanghai Bell |
R4-2201587 |
Reply LS to RAN1: LS on open loop closed loop dual correction of timing |
Ericsson |
R4-2201627 |
Discussion on general issues for NTN RRM |
Huawei, Hisilicon |
R4-2201628 |
CR on general issues for NTN |
Huawei, Hisilicon |
R4-2202563 |
Email discussion summary for [101-bis-e][212] NR_NTN_solutions_RRM_1 |
Moderator (Intel) |
R4-2202637 |
WF on NR NTN RRM requirements |
Qualcomm |
R4-2202638 |
WF on GNSS-related and timing requirements for NR NTN |
Xiaomi |
R4-2202639 |
Reply LS on combination of open and closed loop TA control in NTN |
Qualcomm |
R4-2202729 |
Email discussion summary for [101-bis-e][212] NR_NTN_solutions_RRM_1 |
Moderator (Intel) |
6.13.5.2 |
GNSS-related requirements |
|
R4-2200076 |
Further discussion on GNSS-related requirements |
CATT |
R4-2200804 |
Discussion on NTN GNSS related issues |
CMCC |
R4-2201142 |
Discussion on GNSS-related requirements for NTN |
OPPO |
R4-2201631 |
Discussion on GNSS related issue for NTN |
Huawei, Hisilicon |
R4-2202564 |
Email discussion summary for [101-bis-e][213] NR_NTN_solutions_RRM_2 |
Moderator (Xiaomi) |
R4-2202730 |
Email discussion summary for [101-bis-e][213] NR_NTN_solutions_RRM_2 |
Moderator (Xiaomi) |
6.13.5.3 |
Mobility requirements |
|
R4-2200077 |
Further discussion on mobility requirements for NTN |
CATT |
R4-2200420 |
Mobility requirements |
Qualcomm Incorporated |
R4-2200523 |
Discussion on the mobility aspects for NR NTN UE |
Intel Corporation |
R4-2200679 |
Further discussion on mobility requirements for NR NTN |
Xiaomi |
R4-2200864 |
Discussion on mobility requirement for NR NTN |
LG Electronics UK |
R4-2200892 |
Mobility requirements for NTN |
Ericsson |
R4-2201159 |
Discussion on mobility requirements for NTN |
OPPO |
R4-2201629 |
Discussion on mobility requirements for NTN RRM |
Huawei, Hisilicon |
R4-2201630 |
CR on mobility requirements for NTN |
Huawei, Hisilicon |
6.13.5.4 |
Timing requirements |
|
R4-2200078 |
Further discussion on timing requirements for NTN |
CATT |
R4-2200297 |
Discussion on timing requirements for NR NTN |
Apple |
R4-2200421 |
Timing requirements |
Qualcomm Incorporated |
R4-2200525 |
Discussion on the remaining issues for NTN timing requirements |
Intel Corporation |
R4-2200565 |
Discussion on NTN timing requirements |
LG Electronics Inc. |
R4-2200680 |
Further discussion on timing requirements for NR NTN |
Xiaomi |
R4-2200681 |
DraftCR on timing requirements for NR NTN |
Xiaomi |
R4-2200738 |
Discussion on timing requirements for NTN UE |
ZTE Corporation |
R4-2200805 |
Discussion on NTN timing requirements |
CMCC |
R4-2200931 |
Discussion on timing requirements in NTN |
MediaTek inc. |
R4-2201160 |
Discussion on UL timing requirements for NTN |
OPPO |
R4-2201445 |
On timing advance control |
Nokia, Nokia Shanghai Bell |
R4-2201493 |
LS on Timing Advance control for Rel-17 NTN RRM |
Nokia, Nokia Shanghai Bell |
R4-2201585 |
UE Timing requirements |
Ericsson |
R4-2201586 |
Reply LS to RAN1: LS on NTN UL time and frequency synchronization requirements (Timing) |
Ericsson |
R4-2201610 |
Discussion on UE timing related requirements for NR NTN |
Huawei, Hisilicon |
6.13.5.5 |
Measurement procedure requirements |
|
R4-2200079 |
Further discussion on measurement procedure requirements for NTN |
CATT |
R4-2200298 |
Discussion on measurement procedure requirements for NTN |
Apple |
R4-2200422 |
Measurement procedure requirements |
Qualcomm Incorporated |
R4-2200524 |
Discussion on multiple SMTC and measurement gaps for NTN UE |
Intel Corporation |
R4-2200682 |
Further discussion on measurement requirements for NR NTN |
Xiaomi |
R4-2200865 |
Discussion on NTN measurement requirements |
LG Electronics UK |
R4-2200891 |
Measurement requirements for NTN |
Ericsson |
R4-2201161 |
Discussion on measurement procedure requirements for NTN |
OPPO |
R4-2201632 |
Discussion on measurement requirements for NTN |
Huawei, Hisilicon |
6.13.6 |
Demodulation requirements |
|
R4-2202972 |
Email discussion summary for [101-bis-e][322] NR_NTN_Demod_NWM |
Moderator (Qualcomm) |
R4-2203042 |
WF on general and NTN UE demodulation requirements |
Qualcomm Incorporated |
R4-2203043 |
WF on NTN SAN demodulation requirements |
Huawei, HiSilicon |
R4-2203114 |
Email discussion summary for [101-bis-e][322] NR_NTN_Demod_NWM |
Moderator (Qualcomm) |
6.13.6.1 |
General |
|
R4-2200475 |
Discussion on general issue for NTN NR |
Ericsson |
6.13.6.2 |
Satellite Access Node demodulation requirements |
|
R4-2200171 |
Discussion on Satellite Access Node demodulation requirements |
CATT |
R4-2200476 |
Discussion on satellite access node demodulation requirement for NTN NR |
Ericsson |
R4-2201016 |
Discussion on satellite NTN demod |
Huawei,HiSilicon |
R4-2201785 |
Discussion on Satellite Access Node demodulation requirements for NR NTN |
Intel Corporation |
6.13.6.3 |
UE demodulation requirements |
|
R4-2201015 |
Discussion on UE NTN demod |
Huawei,HiSilicon |
R4-2201420 |
Discussion on UE demodulation for NTN |
Ericsson |
R4-2201786 |
Discussion on UE demodulation requirements for NR NTN |
Intel Corporation |
6.14 |
UE Power Saving Enhancements for NR |
|
R4-2202565 |
Email discussion summary for [101-bis-e][214] NR_UE_pow_sav_enh |
Moderator (MediaTek) |
R4-2202731 |
Email discussion summary for [101-bis-e][214] NR_UE_pow_sav_enh |
Moderator (MediaTek) |
6.14.1 |
General |
|
R4-2200599 |
LS on signalings for enabling RLM and BFD relaxation in R17 UE power saving |
vivo |
R4-2202640 |
WF on RLM/BFD relaxation for UE Power Saving enhancements |
MediaTek Inc. |
R4-2202641 |
LS on signalings for enabling RLM and BFD relaxation in R17 UE power saving |
Vivo, Mediatek |
R4-2202642 |
CR on TS38.133 for applicability of RLM measurement relaxation |
MediaTek inc. |
R4-2202643 |
DraftCR on SSB based relaxed RLM requirements |
Huawei, Hisilicon |
R4-2202644 |
draft CR on CSI-RS RLM requirements relaxation for R17 UE power saving |
vivo |
R4-2202645 |
38.133 draft CR on RLM relaxation criteria |
Nokia, Nokia Shanghai Bell |
R4-2202646 |
Draft CR: Applicability rule for relaxed BFD requirements |
Ericsson |
R4-2202647 |
Draft CR for TS 38.133 Minimum requirement for SSB based BFD for UE configured with relaxed measurement criterion |
CMCC |
R4-2202648 |
Draft CR Minimum requirement for CSI-RS based beam failure detection for UE configured with relaxed measurement criterion |
Xiaomi |
R4-2202649 |
Draft CR on relaxed measurement criteria for BFD |
CATT |
R4-2202759 |
Draft Big CR: RRM requirements Rel-17 NR UE Power Saving Enhancements |
MediaTek |
R4-2202769 |
LS on signaling for enabling RLM and BFD relaxation in R17 UE power saving |
vivo |
6.14.2 |
RRM core requirements |
|
R4-2200325 |
On Power Saving RRM Requirement |
Qualcomm, Inc. |
R4-2200530 |
Discussion on NR UE power saving for RLM and BM |
Intel Corporation |
6.14.2.1 |
UE measurements relaxation for RLM and/or BFD |
|
R4-2200105 |
Further discussion on RLM/BFD relaxation for UE power saving enhancement |
CATT |
R4-2200106 |
Draft CR on relaxed measurement criteria for BFD |
CATT |
R4-2200258 |
UE measurements relaxation for RLM and/or BFD |
Apple |
R4-2200600 |
Discussion on RLM and BFD relaxation for NR UE power saving |
vivo |
R4-2200601 |
draft CR on CSI-RS RLM requirements relaxation for R17 UE power saving |
vivo |
R4-2200685 |
Further discussion on UE measurements relaxation for RLM and/or BFD |
Xiaomi |
R4-2200686 |
Draft CR Minimum requirement for CSI-RS based beam failure detection for UE configured with relaxed measurement criterion |
Xiaomi |
R4-2200797 |
Draft CR for TS 38.133 Minimum requirement for SSB based BFD for UE configured with relaxed measurement criterion |
CMCC |
R4-2200806 |
Discussion on RLM/BFD relaxation for NR power saving enhancement |
CMCC |
R4-2200896 |
Discussion about RLM/BFD measurement relaxation |
Nokia, Nokia Shanghai Bell |
R4-2200897 |
38.133 draft CR on RLM relaxation criteria |
Nokia, Nokia Shanghai Bell |
R4-2201143 |
Discussion on RRM requirements for R17 RLM/BFD relaxation |
OPPO |
R4-2201406 |
RLM and RLF relaxation for UE power saving |
ZTE Corporation |
R4-2201611 |
Discussion on UE measurement relaxation for RLM/BFD |
Huawei, Hisilicon |
R4-2201612 |
DraftCR on SSB based relaxed RLM requirements |
Huawei, Hisilicon |
R4-2201867 |
Discussions on UE power saving for RLM and BFD |
Ericsson |
R4-2201868 |
Draft CR: Applicability rule for relaxed BFD requirements |
Ericsson |
R4-2201962 |
Discussion on Rel-17 RLM/BFD measurement relaxation |
MediaTek inc. |
R4-2201963 |
CR on TS38.133 for applicability of RLM measurement relaxation |
MediaTek inc. |
6.15.1 |
General |
|
R4-2200833 |
TR38.785 v0.5.0 TR Update for SL enhancement in Rel-17 |
LG Electronics France |
R4-2200946 |
TP for TR 38.785: Addition of definitions and symbols to Chapter 3 |
vivo |
R4-2202224 |
Email discussion summary for [101-bis-e][124] NRSL_enh_Part_1 |
Moderator (LGE) |
R4-2202324 |
Email discussion summary for [101-bis-e][124] NRSL_enh_Part_1 |
Moderator (LGE) |
R4-2202355 |
TP for TR 38.785: Addition of definitions and symbols to Chapter 3 |
vivo |
R4-2202360 |
WF on switching time mask and sync issue for intra-band V2X con-current operation |
CATT |
R4-2202361 |
WF on configured transmitted power for intra-band V2X con-current operation |
LG Electronics |
R4-2202362 |
WF on MPR for intra-band V2X con-current operation |
Huawei, HiSilicon |
6.15.2 |
UE RF requirements for NR SL enhancement |
|
R4-2200842 |
TP on RF requirements for NR PS UE in n14 for NRSL_enh WI in Rel-17 |
LG Electronics France |
R4-2200848 |
Draft CR on RF requirements for SL enhancement for public safety service in n14 |
LG Electronics France |
R4-2202407 |
TP on RF requirements for NR PS UE in n14 for NRSL_enh WI in Rel-17 |
LG Electronics France |
R4-2202408 |
Draft CR on RF requirements for SL enhancement for public safety service in n14 |
LG Electronics France |
6.15.2.2 |
REFSENS requirements |
|
R4-2200509 |
n14 REFSENS for PS in licensed band |
Qualcomm Incorporated |
6.15.2.3 |
Other RF requirements |
|
R4-2200138 |
Draft CR for TS 38.101-1, Correction on MOP requirements for inter-band V2X con-current operation (Rel-17) |
CATT |
R4-2200139 |
Draft CR for TS 38.101-1, Correction on MOP requirements for inter-band V2X con-current operation (Rel-16) |
CATT |
R4-2200140 |
Draft CR for TS 38.101-3, Correction on MOP requirements for inter-band V2X con-current operation (Rel-17) |
CATT |
R4-2200141 |
Draft CR for TS 38.101-3, Correction on MOP requirements for inter-band V2X con-current operation (Rel-16) |
CATT |
R4-2201952 |
TP for 38.785: TxD requirements for NR V2X |
Huawei, HiSilicon |
R4-2201953 |
Big CR: introduction of TxD requirements for NR V2X |
Huawei, HiSilicon |
6.15.3 |
Intra-band con-current operation between NR SUL and NR Uu |
|
R4-2200841 |
Draft CR on RF requirements for intra-band con-current V2X operation in Rel-17 |
LG Electronics France |
R4-2202356 |
Draft CR on RF requirements for intra-band con-current V2X operation in Rel-17 |
LG Electronics |
R4-2202357 |
TP on RF requirements for intra-band con-current V2X operation in licensed band |
LG Electronics |
R4-2202358 |
draft CR for TS 38.101-1 correction on intra-band concurrent operation |
Xiaomi |
R4-2202359 |
TP on sync issue for intra-band V2X operation |
CATT |
6.15.3.1 |
RF requirements for intra-band V2X con-current (including MPR) |
|
R4-2200143 |
TP on configured transmitted power for intra-band V2X con-current operation |
CATT |
R4-2200556 |
MPR for NR V2X intra-band con-current operation with Uu |
LG Electronics |
R4-2200834 |
RF requirements for intra-band con-current V2X operation in licensed band |
LG Electronics France |
R4-2200840 |
TP on RF requirements for intra-band con-current V2X operation in licensed band |
LG Electronics France |
R4-2200947 |
Remaining issues for intra-band con-current operation |
vivo |
R4-2201496 |
draft CR for TS 38.101-1 correctiron on intra-band concurrent operation |
Xiaomi |
R4-2201500 |
further discussion on configured power for intra-band concurrent operation |
Xiaomi |
R4-2201949 |
Draft CR for TS 38.101-1: configured transmitted power for intra-band con-current operation |
Huawei, HiSilicon |
R4-2201950 |
MPR for intra-band con-current operation |
Huawei, HiSilicon |
6.15.3.2 |
Synchronous operation between SL and Uu (including switching time mask, SL transmission timing) |
|
R4-2200142 |
Discussion on time mask for Uu and SL switching |
CATT |
R4-2200510 |
RF switching time for V2X intra-band con-current operation with different carriers in TDD bands and time masks for same carrier switching |
Qualcomm Incorporated |
R4-2201021 |
TP on sync issue for intra-band V2X operation |
CATT |
R4-2201497 |
draft CR for TS 38.101-1 on switching time mask between SL and Uu |
Xiaomi |
R4-2201502 |
further discussion on switching time mask between SL and Uu |
Xiaomi |
R4-2201948 |
On SL switching time mask |
Huawei, HiSilicon |
6.15.4 |
High power UE(PC2) for SL |
|
R4-2202225 |
Email discussion summary for [101-bis-e][125] NRSL_enh_Part_2 |
Moderator (CATT) |
R4-2202325 |
Email discussion summary for [101-bis-e][125] NRSL_enh_Part_2 |
Moderator (CATT) |
R4-2202363 |
WF on PC2 HPUE for NR sidelink enhancements |
Huawei |
6.15.4.1 |
TX requirements (Power class) |
|
R4-2201498 |
draft CR for TS 38.101-3 on Pcmax definition on inter-band V2X UE |
Xiaomi |
R4-2201501 |
further discussion on Pcmax definition on inter-band V2X UE |
Xiaomi |
6.15.4.2 |
Coexistence study |
|
R4-2201499 |
further discussion on co-existence issue for HPUE |
Xiaomi |
R4-2201708 |
Co-channel existing |
Ericsson |
R4-2201951 |
On co-channel existence issue in RAN4 |
Huawei, HiSilicon |
6.15.5 |
RRM core requirements |
|
R4-2200326 |
On NR SL RRM Requirement |
Qualcomm, Inc. |
R4-2202226 |
Email discussion summary for [101-bis-e][126] NRSL_enh_Part_3 |
Moderator (Huawei) |
R4-2202326 |
Email discussion summary for [101-bis-e][126] NRSL_enh_Part_3 |
Moderator (Huawei) |
R4-2202566 |
Email discussion summary for [101-bis-e][215] NR_SL_enh_RRM |
Moderator (LGE) |
R4-2202650 |
WF on NR SL enhancements RRM requirements |
LG Electronics |
R4-2202651 |
Draft CR on UE transmit timing requirements for sidelink enhancement |
CATT |
R4-2202652 |
draft CR on interruption requirement for SL |
LG Electronics |
R4-2202653 |
Draft CR on requirements for InitiationCease of SLSS Transmissions impact by SL-DRX |
Xiaomi |
R4-2202654 |
Draft CR on Selection Reselction of V2X Synchronization Reference Source for sidelink enhancement |
vivo |
R4-2202655 |
DraftCR on scheduling availability requirements for NR eV2X |
Huawei, Hisilicon |
R4-2202656 |
CR: SL autonomous resource allocation requirements (draft CR) |
Qualcomm communications-France |
R4-2202732 |
Email discussion summary for [101-bis-e][215] NR_SL_enh_RRM |
Moderator (LGE) |
R4-2202747 |
Draft Big CR: RRM requirements for Rel-17 NR SL enhancement |
LG Electronics |
6.15.5.1 |
Intra-band con-current V2X operation |
|
R4-2200107 |
Draft CR on UE transmit timing requirements for sidelink enhancement |
CATT |
R4-2200687 |
Further discussion on RRM requirements for intra-band con-current V2X operation |
Xiaomi |
R4-2201144 |
Discussion on RRM impact of intra-band concurrent V2X operation |
OPPO |
R4-2201365 |
Further discussion on Intra-band con-current V2X operation RRM requirements |
vivo |
R4-2201404 |
RRM requirements for FDM based intra-band con-current SL operation |
ZTE Corporation |
R4-2201613 |
Discussion on RRM requirements related to intra-band con-current V2X operation |
Huawei, Hisilicon |
6.15.5.2 |
SL-DRX |
|
R4-2200108 |
Further discussion on RRM requirements related to SL-DRX |
CATT |
R4-2200557 |
RRM requirements for SL-DRX |
LG Electronics |
R4-2200688 |
Further discussion on RRM requirements related to SL-DRX |
Xiaomi |
R4-2201162 |
Discussion on SL-DRX |
OPPO |
R4-2201366 |
Further discussion on SL-DRX RRM requirements |
vivo |
R4-2201367 |
Draft CR on Selection Reselction of V2X Synchronization Reference Source for sidelink enhancement |
vivo |
R4-2201403 |
Discussions on DRX in NR SL enhancement |
ZTE Corporation |
R4-2201614 |
Discussion on RRM requirements related to SL DRX |
Huawei, Hisilicon |
R4-2201871 |
Discussions on SL DRX for Rel-17 SL operation |
Ericsson |
6.15.5.3 |
Others |
|
R4-2200109 |
Discussion on L1-RSRP measurement for sidelink enhancement |
CATT |
R4-2200558 |
draft CR on interruption requirement for SL |
LG Electronics |
R4-2200689 |
Draft CR on requirements for InitiationCease of SLSS Transmissions impact by SL-DRX |
Xiaomi |
R4-2201615 |
DraftCR on scheduling availability requirements for NR eV2X |
Huawei, Hisilicon |
R4-2202021 |
CR: SL autonomous resource allocation requirements |
Qualcomm communications-France |
6.16.1 |
General |
|
R4-2200469 |
Views on sensing beam selection on the UE side |
Sony |
R4-2200847 |
Draft LS on sensing beam characteristics to RAN1 |
Ericsson |
R4-2200948 |
Draft CR for TS 38.101-2: Introduction of system parameters for FR2-2 |
vivo |
R4-2201410 |
Discussion and draft reply LS on sensing beam selection from RAN1 |
Huawei, HiSilicon |
R4-2201533 |
Discussion and draft reply LS on sensing beam selection from RAN1 |
Huawei, HiSilicon |
R4-2201923 |
CR work split and UE feature list for NR ext. to 71GHz |
Intel Corporation |
R4-2202227 |
Email discussion summary for [101-bis-e][127] NR_ext_to_71GHz_Part_1 |
Moderator (Intel) |
R4-2202327 |
Email discussion summary for [101-bis-e][127] NR_ext_to_71GHz_Part_1 |
Moderator (Intel) |
R4-2202364 |
Draft CR for TS 38.101-2: Introduction of system parameters for FR2-2 |
Vivo |
R4-2202365 |
WF on general aspects and system parameters of FR2-2 |
Intel |
R4-2202409 |
Draft LS on sensing beam characteristics to RAN1 |
Ericsson |
6.16.2 |
Operation bands and system parameters (channelization, raster, CBW, etc) |
|
R4-2200080 |
Discussion of channelization for up to 71 GHz |
CATT |
R4-2200081 |
LS for the channelization for up to 71 GHz |
CATT |
R4-2200282 |
Channel and Sync rasters for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2200321 |
draft CR to 38.101-2 60 GHz UE general clauses |
Qualcomm Incorporated |
R4-2200863 |
Channel arrangement and channel bandwidths for n263 |
Ericsson |
R4-2200949 |
Further discussion on channel raster and sync raster for 52.6~71 GHz |
vivo |
R4-2201490 |
Draft CR to TS 38.104: Section 5.4 Channel arrangement |
Ericsson |
R4-2201491 |
52.6-71 GHz System Parameters |
Ericsson |
R4-2201592 |
60GHz channel and synchronization raster |
LG Electronics Finland |
R4-2201598 |
System parameters for a NR band in the range 52.6GHz – 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2201924 |
Views on channelization for 52.6 to 71 GHz |
Intel Corporation |
R4-2201985 |
Channelization and synchronization raster for 60GHz |
MediaTek (Chengdu) Inc. |
R4-2202023 |
Discussion on the channel raster and sync raster in FR2-2 |
Huawei |
R4-2202411 |
Channel arrangement and channel bandwidths for n263 |
Ericsson |
R4-2202412 |
Draft CR to TS 38.104: Section 5.4 Channel arrangement |
Ericsson |
6.16.3 |
UE RF requirements |
|
R4-2200438 |
UE antenna module with 60 GHz integration |
Apple |
R4-2202228 |
Email discussion summary for [101-bis-e][128] NR_ext_to_71GHz_Part_2 |
Moderator (Qualcomm) |
R4-2202328 |
Email discussion summary for [101-bis-e][128] NR_ext_to_71GHz_Part_2 |
Moderator (Qualcomm) |
6.16.3.1 |
TX requirements |
|
R4-2200067 |
Views on UE antenna elements for FR2-2 |
Murata Manufacturing Co Ltd. |
R4-2200238 |
60GHz UE TX |
Qualcomm Incorporated |
R4-2200312 |
draft CR to 38.101-2 60 GHz UE TX |
Qualcomm Incorporated |
R4-2200453 |
Remaining issues with transient requirements for FR2-2 |
Apple |
R4-2200470 |
UE Array, EIRP level and Spherical Coverage at 60 GHz |
Sony, Ericsson |
R4-2200570 |
View on TX requirements of FR2-2 |
MediaTek Beijing Inc. |
R4-2200950 |
Further discussion on handheld UE EIRP and spherical coverage requirements for 52.6~71 GHz |
vivo |
R4-2201073 |
On UE Tx RF aspects for a NR band in the range 52.6GHz – 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2201209 |
Discussion on Tx RF requirements in FR2-2 |
LG Electronics Finland |
R4-2201411 |
On 60GHz UE Tx RF requirements |
Huawei, HiSilicon |
R4-2201534 |
On 60GHz UE Tx RF requirements |
Huawei, HiSilicon |
R4-2201925 |
UE Tx requirements for 52.6 to 71 GHz |
Intel Corporation |
R4-2202247 |
60GHz UE TX |
Qualcomm Incorporated |
R4-2202269 |
R17 60GHz Tx requirements |
OPPO |
R4-2202366 |
WF on 60 GHz UE RF |
Qualcomm |
R4-2202402 |
On EIRP for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2202414 |
Peak EIRP and EIS for 60 GHz |
Apple |
6.16.3.2 |
RX requirements |
|
R4-2200239 |
60 GHz UE RX |
Qualcomm Incorporated |
R4-2200307 |
draft CR to 38.101-2 60GHz UE RX |
Qualcomm Incorporated |
R4-2200360 |
Handheld UE antenna assumption for FR2-2 |
NTT DOCOMO, INC. |
R4-2200951 |
Further discussion on handheld UE EIS requirements for 52.6~71 GHz |
vivo |
R4-2201171 |
Discussion on Rx RF requirements in FR2-2 |
LG Electronics Finland |
R4-2201412 |
On 60GHz UE EIS requirements |
Huawei, HiSilicon |
R4-2201535 |
On 60GHz UE EIS requirements |
Huawei, HiSilicon |
R4-2201926 |
UE EIS requirements for FR2-2 |
Intel Corporation |
R4-2202248 |
60 GHz UE RX |
Qualcomm Incorporated |
R4-2202403 |
On EIS for FR2-2 |
Nokia, Nokia Shanghai Bell |
6.16.4 |
BS RF requirements |
|
R4-2202973 |
Email discussion summary for [101-bis-e][309] NR_exto71GHz_BSRF |
Moderator (Nokia) |
R4-2203115 |
Email discussion summary for [101-bis-e][309] NR_exto71GHz_BSRF |
Moderator (Nokia) |
6.16.4.1 |
TX requirements |
|
R4-2200136 |
Discussion on BS TX RF requirements for 52 6-71GHz |
CATT |
R4-2200411 |
Proposals on BS transmitter requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2200414 |
Draft CR to TR 38.104: Clauses 9.1 to 9.5 |
Nokia, Nokia Shanghai Bell |
R4-2200843 |
On BS RF transmitter requirements for the frequency range 52 to 71 GHz |
Ericsson |
R4-2200845 |
Draft CR to TS 38.104: Addition of requirements for NR extension up to 71 GHz in subclause 9.6 to 9.8 |
Ericsson |
R4-2201456 |
Further discussion on BS Tx requirements for 52.6-71GHz |
ZTE Corporation |
R4-2201821 |
Discussion on the remaining BS RF requirements for FR2-2: Tx requirements |
Huawei |
R4-2203012 |
Draft CR to TR 38.104: Clauses 9.1 to 9.5 |
Nokia, Nokia Shanghai Bell |
R4-2203013 |
Draft CR to TS 38.104: Addition of requirements for NR extension up to 71 GHz in subclause 9.6 to 9.8 |
Ericsson |
6.16.4.2 |
RX requirements |
|
R4-2200137 |
Discussion on BS RX RF requirements for 52 6-71GHz |
CATT |
R4-2200151 |
Draft CR for TS 38.104 on introduction of BS RF Rx requirements for 57-71GHz in section 10.1 – 10.5 |
CATT |
R4-2200412 |
Proposals on BS receiver requirements for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2200844 |
On BS RF receiver requirements for the frequency range 52 to 71 GHz |
Ericsson |
R4-2201457 |
Further discussion on BS Rx requirements for 52.6-71GHz |
ZTE Corporation |
R4-2201822 |
Discussion on the remaining BS RF requirements for FR2-2: Rx requirements |
Huawei |
R4-2201823 |
Draft CR to TS 38.104: implementation of FR2-2 requirements: FRC annex |
Huawei |
R4-2203014 |
Draft CR to TS 38.104: implementation of FR2-2 requirements: FRC annex |
Huawei |
R4-2203015 |
Draft CR for TS 38.104 on introduction of BS RF Rx requirements for 57-71GHz in section 10.1 – 10.5 |
CATT |
R4-2203016 |
WF on BS RF Tx requirements |
Nokia, Nokia Shanghai Bell |
R4-2203017 |
WF on BS RF Rx requirements |
Ericsson |
6.16.5 |
Co-existence simulations |
|
R4-2200039 |
Discussions on coexistence requirements for 60GHz |
Qualcomm CDMA Technologies |
R4-2200082 |
Discussion on ACIR requirement for 71 GHz |
CATT |
R4-2200413 |
Proposals on coexistence simulation for extending current NR operation to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2200578 |
Discussion on ACIR requirements for 52.6-71 GHz |
Korea Testing Laboratory |
R4-2200846 |
Update of coexistence simulation results relevant for NR extension to 71 GHz |
Ericsson |
R4-2200952 |
Discussion on DL/UL ACIR and BS/UE ACLR/ACS for FR2-2 |
vivo |
R4-2201455 |
Coexistence simulation results for 52.6-71GHz |
ZTE Corporation |
R4-2202229 |
Email discussion summary for [101-bis-e][129] NR_ext_to_71GHz_Part_3 |
Moderator (CATT) |
R4-2202329 |
Email discussion summary for [101-bis-e][129] NR_ext_to_71GHz_Part_3 |
Moderator (CATT) |
R4-2202367 |
WF on the decision of DL/UL ACIR and BS/UE ACLR/ACS for FR2-2 |
CATT, Qualcomm, Nokia, ZTE, Ericsson, vivo, Korea Testing Laboratory, Huawei |
6.16.6 |
FR1+FR2-2 DC/CA band combinations |
|
R4-2201599 |
How to introduce FR2-2 bands into 38.101-2 and combinations into 38.101-3 |
Nokia, Nokia Shanghai Bell |
R4-2201916 |
Discussion on FR2-2 DC/CA with FR1 anchor |
Ericsson |
R4-2201917 |
draft CR 38.101-3 on FR2-2 DC/CA with FR1 anchor |
Ericsson |
R4-2202410 |
draft CR 38.101-3 on FR2-2 DC/CA with FR1 anchor |
Ericsson |
6.16.7 |
RRM core requirements |
|
R4-2200660 |
Reply LS on the minimum time gap for wake-up and Scell dormancy indication for NR operation in 52.6 to 71GHz |
vivo |
6.16.7.1 |
General |
|
R4-2200125 |
Further discussion on General RRM requirements for extension to 71GHz |
CATT |
R4-2200562 |
Discussion on general RRM measurement requirements for extension to 71GHz |
LG Electronics Inc. |
R4-2200654 |
Further discussion on RRM impacts for extending NR operation to 71GHz |
vivo |
R4-2200655 |
Draft CR to 38.133 Introducing applicability of requirements for FR2 |
vivo |
R4-2200888 |
General RRM requirements for extending NR operation to 71GHz |
Ericsson |
R4-2200889 |
On general measurement requriement for extending NR operation to 71GHz |
Ericsson |
R4-2200914 |
Discussion on general RRM requirements for extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2200932 |
Discussion on RRM requirements in FR2-2 |
MediaTek inc. |
R4-2200933 |
Introduction of scheduling restriction for FR2-2 |
MediaTek inc. |
R4-2201194 |
Discussion on general RRM requirements for FR2-2 |
Huawei, Hisilicon |
R4-2202567 |
Email discussion summary for [101-bis-e][216] NR_ext_to_71GHz_RRM_1 |
Moderator (Qualcomm) |
R4-2202657 |
WF on NR extension to 71 GHz RRM requirements (Part 1) |
Qualcomm |
R4-2202658 |
LS on UE transmit timings |
Nokia |
R4-2202661 |
Draft CR to 38.133 Introducing interruption requirements of FR2-2 to cover 52.6-71GHz |
vivo |
R4-2202662 |
Draft CR on BWP switching requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2202663 |
DraftCR on general measurement requriement for extending NR operation to 71GHz |
Ericsson |
R4-2202733 |
Email discussion summary for [101-bis-e][216] NR_ext_to_71GHz_RRM_1 |
Moderator (Qualcomm) |
R4-2202754 |
Draft Big CR: RRM requirements for Rel-17 NR extension to 71GHz |
Qualcomm, Intel |
R4-2202755 |
Draft CR to 38.133 Introducing applicability of requirements for FR2 |
Vivo |
R4-2202757 |
Draft CR to 38.133 Introduction of scheduling restriction for FR2-2 |
Mediatek |
6.16.7.2 |
Timing requirements |
|
R4-2200126 |
Further discussion on RRM timing requirements for higher SCS |
CATT |
R4-2200283 |
UE transmit timing for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2200563 |
Discussion on MTTD/MRTD for extension to 71GHz |
LG Electronics Inc. |
R4-2200661 |
Further discussion on timing for 52.6-71GHz |
vivo |
R4-2200915 |
Discussion on RRM timing requirements for extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2200916 |
Draft CR adding timing requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2200934 |
Discussion on timing requirements in FR2-2 |
MediaTek inc. |
R4-2201195 |
Discussion on timing requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2201407 |
On Te requirements for NR systems extended to 71 GHz |
ZTE Corporation |
R4-2201583 |
UE Timing requirements |
Ericsson |
R4-2201787 |
Discussion on timing requirements for NR 52.6 – 71 GHz |
Intel Corporation |
R4-2202033 |
Timing requirements in FR2-2 |
Qualcomm Incorporated |
R4-2202048 |
Draft CR for timing requirements for FR2-2 – MRTD, MTTD |
Qualcomm Incorporated |
R4-2202756 |
Draft CR to 38.133 Timing requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
6.16.7.3 |
Interruption requirements |
|
R4-2200656 |
Furthr discussion on interruption for 52.6-71GHz |
vivo |
R4-2200657 |
Draft CR to 38.133 Introducing interruption requirements of FR2-2 to cover 52.6-71GHz |
vivo |
R4-2200885 |
Interruption requirements for extending NR operation to 71GHz |
Ericsson |
R4-2200917 |
Discussion on interruption requirements for FR2-2 |
Nokia, Nokia Shanghai Bell |
R4-2201196 |
Discussion on interruption requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2201788 |
Discussion on interruption requirements for NR 52.6 – 71 GHz |
Intel Corporation |
R4-2202568 |
Email discussion summary for [101-bis-e][217] NR_ext_to_71GHz_RRM_2 |
Moderator (Intel) |
R4-2202659 |
WF on NR extension to 71 GHz RRM requirements (Part 2) |
Intel |
R4-2202660 |
Reply LS on the minimum time gap for wake-up and Scell dormancy indication for NR operation in 52.6 to 71GHz |
vivo |
R4-2202734 |
Email discussion summary for [101-bis-e][217] NR_ext_to_71GHz_RRM_2 |
Moderator (Intel) |
6.16.7.4 |
Active BWP switching delay requirements |
|
R4-2200127 |
Discussion on cross-carrier active BWP switching for extension to 71GHz |
CATT |
R4-2200284 |
Active BWP switch delay for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2200658 |
Further discussion on active BWP switching delay for 52.6-71GHz |
vivo |
R4-2200872 |
On cross-carrier BWP switch delay for extension to 71 GHz |
Nokia, Nokia Shanghai Bell |
R4-2200887 |
Active BWP switching delay requirements for extending NR operation to 71GHz |
Ericsson |
R4-2201197 |
Discussion on BWP switching requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2201198 |
Draft CR on BWP switching requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2201409 |
Active BWP switching delay requirements for NR systems extended to 71 GHz |
ZTE Corporation |
R4-2201789 |
Discussion on BWP switching delay for NR 52.6 – 71 GHz |
Intel Corporation |
6.16.7.5 |
Measurement gap interruption requirements |
|
R4-2200659 |
Further discussion on measurement gap interruption for 52.6-71GHz |
vivo |
R4-2200886 |
Measurement gap interruption requirements for extending NR operation to 71GHz |
Ericsson |
R4-2201199 |
Discussion on measurement gap interruption requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
6.16.7.6 |
LBT impacts on RRM requirements |
|
R4-2200285 |
LBT impacts on RRM requirements for NR operation in 52.6GHz - 71GHz |
Apple |
R4-2200873 |
LBT impacts on NR RRM requirements for extension to 71GHz |
Nokia, Nokia Shanghai Bell |
R4-2201200 |
Discussion on LBT impacts on RRM requirements for extending NR operation to 71GHz |
Huawei, Hisilicon |
R4-2201371 |
Discussion on LBT requirements for FR2-2 |
vivo |
R4-2201408 |
On LBT impacts on RRM for NR systems extended to 71 GHz |
ZTE Corporation |
R4-2201790 |
Discussion on LBT impacts on RRM requirements for NR 52.6 – 71 GHz |
Intel Corporation |
R4-2201791 |
DraftCR on LBT impacts on RRM requirements for NR 52.6 – 71 GHz |
Intel Corporation |
6.16.8 |
Others |
|
R4-2200083 |
Discussion on the LBT requirement and the reply LS for sensing beam selection |
CATT |
R4-2200084 |
Draft CR for TS 37.107: introduction of LBT requirements for FR2-2 |
CATT |
R4-2200085 |
Draft CR for TS 37.106: introduction of LBT requirements for FR2-2 |
CATT |
R4-2200953 |
Discussion and draft reply LS on sensing beam selection |
vivo |
R4-2201600 |
Sensing beam for LBT in FR2-2 |
Nokia, Nokia Shanghai Bell |
6.17.1 |
General |
|
R4-2201702 |
LS response on range of power control parameters for eIAB |
Ericsson |
R4-2203018 |
WF on work split for eIAB RF impact to TS38.174 |
Samsung |
R4-2203019 |
WF on timing enhancement for eIAB |
Nokia |
R4-2203020 |
LS on range of power control parameters for eIAB |
Samsung |
6.17.2.1 |
Impact for Simultaneous operation of IAB child and parent links |
|
R4-2200936 |
Specification impact due to IAB simultaneous operation |
Samsung |
R4-2201595 |
RF requirements due to Tx power imbalance between IAB-MT and IAB-DU |
Nokia, Nokia Shanghai Bell |
R4-2201700 |
RF core specification impact for Simultaneous operation of DU and MT |
Ericsson |
R4-2202664 |
WF on RRM requirements for IAB enhancement |
ZTE Corporation |
R4-2202665 |
Draft CR on timing requirements for Rel-17 IAB |
Huawei, Hisilicon |
6.17.2.2 |
Impact for Timing enhancement |
|
R4-2200839 |
Discussion on timing issues for simultaneous operation of IAB |
ZTE Corporation |
R4-2200937 |
Discussion on timing enhancement |
Samsung |
R4-2201596 |
Discussion on timing error for eIAB |
Nokia, Nokia Shanghai Bell |
R4-2201701 |
IAB MT /DU case 6 timing |
Ericsson |
R4-2201939 |
eIAB Timing error between MT TX and DU TX |
Huawei |
6.17.2.3 |
Others |
|
R4-2200938 |
Discussion on range of power control parameters for Rel-17 eIAB |
Samsung |
R4-2201597 |
Draft reply LS to RAN1 on Power control parameters |
Nokia, Nokia Shanghai Bell |
6.17.3 |
RRM core requirements |
|
R4-2201206 |
Discussion on RRM requirements for eIAB |
Huawei, Hisilicon |
R4-2201207 |
Draft CR on timing requirements for Rel-17 IAB |
Huawei, Hisilicon |
R4-2201405 |
On RRM for eIAB |
ZTE Corporation |
R4-2201849 |
On IAB Enhanced RRM Requirements |
Nokia, Nokia Shanghai Bell |
R4-2201850 |
TP to TS 38.174 on RRM Timing Requirements |
Nokia, Nokia Shanghai Bell |
R4-2202019 |
Further analysis of RRM requirements for enhanced IAB |
Ericsson |
R4-2202052 |
CLI measurement requirement for R17 NR eIAB RRM |
Qualcomm CDMA Technologies |
R4-2202569 |
Email discussion summary for [101-bis-e][218] NR_IAB_enh_RRM |
Moderator (ZTE) |
R4-2202735 |
Email discussion summary for [101-bis-e][218] NR_IAB_enh_RRM |
Moderator (ZTE) |
R4-2203353 |
CLI measurement requirement for R17 NR eIAB RRM |
Qualcomm CDMA Technologies |
6.18 |
NR coverage enhancements |
|
R4-2202230 |
Email discussion summary for [101-bis-e][130] NR_cov_enh |
Moderator (China Telecom) |
R4-2202330 |
Email discussion summary for [101-bis-e][130] NR_cov_enh |
Moderator (China Telecom) |
6.18.1 |
General and CR structure |
|
R4-2200020 |
Updated RAN4 RF work plan for NR coverage enhancements WI |
China Telecom |
R4-2200339 |
draft CR for EVM based requriements |
Qualcomm Incorporated |
R4-2201706 |
simulation updated results for phase tolerance for PUSCH repetition |
Ericsson |
R4-2202368 |
Reply LS on Maximum duration for DMRS bundling |
Qualcomm Incorporated |
R4-2202369 |
WF on phase continuity and power consistency for PUCCH and PUSCH transmissions |
Huawei, HiSilicon |
R4-2202418 |
WF on phase continuity and power consistency for PUCCH and PUSCH transmissions |
Huawei, HiSilicon |
6.18.2 |
UE RF requirements |
|
R4-2201986 |
Some remaining open issues on coverage enhancements |
MediaTek (Chengdu) Inc. |
6.18.2.1 |
Requirements for non-scheduled gap |
|
R4-2200021 |
RF requirements for the non-zero gap in between PUSCH/PUCCH transmissions |
China Telecom |
R4-2200343 |
OFF power requirement for the gap in TX on case |
Qualcomm Incorporated |
R4-2201705 |
RF impact on non-scheduled gap |
Ericsson |
6.18.2.2 |
Tolerance for power consistency/phase continuity |
|
R4-2200022 |
On phase continuity and power consistency tolerance |
China Telecom |
R4-2200338 |
Discussion on UE requirement for JCE |
Qualcomm Incorporated |
R4-2200471 |
Views on phase continuity and power consistency for PUSCH and PUCCH repetition |
Sony |
R4-2200926 |
Discussion on testability of coverage enhancement requirements |
ROHDE & SCHWARZ |
R4-2201704 |
On JCE phase continuity and power consistency tolerance for PUCCH and PUSCH |
Ericsson |
R4-2201840 |
Feasibility of proposed test methods for phase continuity and power consistency tolerance measurements |
Anritsu Limited |
R4-2201958 |
On phase continuity for multiple transmissions |
Huawei, HiSilicon |
6.18.2.3 |
Maximum duration for joint channel estimation |
|
R4-2200023 |
On maximum duration for joint channel estimation |
China Telecom |
R4-2201707 |
LS reply On maximum duration of phase continuity and power consistency for PUCCH and PUSCH repetition |
Ericsson |
6.18.2.4 |
Others |
|
R4-2200024 |
On UE autonomous adjustment and DL reception in-between transmission |
China Telecom |
R4-2200344 |
Maximum duration handling for JCE |
Qualcomm Incorporated |
R4-2201703 |
On measurement of the TX coherent transmission |
Ericsson |
6.18.3 |
BS demodulation requirements |
|
R4-2200025 |
BS demodulation requirements for NR coverage enhancements |
China Telecom |
R4-2200408 |
BS demodulation requirements for NR coverage enhancements |
Nokia, Nokia Shanghai Bell |
R4-2200477 |
Discussion on BS demodulation requirements for NR coverage enhancement |
Ericsson |
R4-2200756 |
View on demodulation requirement for Rel-17 coverage enhancement |
Samsung |
R4-2201017 |
Discussion on BS coverage enhancement demod |
Huawei,HiSilicon |
R4-2201604 |
Discussion on scope of BS demodulation requirements for NR coverage enhancements WI |
Intel Corporation |
R4-2202975 |
Email discussion summary for [101-bis-e][319] NR_cov_enh_Demod_NWM |
Moderator (China Telecom) |
R4-2203030 |
WF on PUSCH demodulation performance of Rel-17 NR coverage enhancement |
China Telecom |
R4-2203031 |
WF on PUCCH demodulation performance of Rel-17 NR coverage enhancement |
Nokia |
R4-2203117 |
Email discussion summary for [101-bis-e][319] NR_cov_enh_Demod_NWM |
Moderator (China Telecom) |
6.19.1 |
General |
|
R4-2200276 |
Discussion on Impact to RF and RRM requirements with simultaneous reception |
Apple |
R4-2200534 |
Discussion on FR2 simultaneous reception in NR FeMIMO |
Intel Corporation |
R4-2200924 |
FR2 UE with the capability of simultaneous reception with different QCL Type-D RSs |
Samsung |
R4-2201266 |
Requirements for Simultaneous Reception in FR2 |
Qualcomm Incorporated |
R4-2201386 |
Discussion on Simultaneous reception with different QCL-type D |
Ericsson |
R4-2202231 |
Email discussion summary for [101-bis-e][131] NR_feMIMO |
Moderator (Samsung) |
R4-2202331 |
Email discussion summary for [101-bis-e][131] NR_feMIMO |
Moderator (Samsung) |
R4-2202370 |
WF on remaining issues of FeMIMO |
Sasmsung |
R4-2202413 |
LS on Rel-17 FeMIMO SRS related impact |
Huawei |
6.19.2 |
UE RF requirements |
|
R4-2200925 |
On RF requirements for further enhancements on MIMO |
Samsung |
6.19.2.1 |
Additional requirement for multi-panel reception |
|
R4-2200568 |
View on additional FR2 FeMIMO multi-panel reception requirement |
MediaTek Beijing Inc. |
R4-2200591 |
Discussion on Additional requirement for multi-panel reception |
ZTE Corporation |
R4-2200962 |
Further discussion on impact of multi-panel reception requirements |
vivo |
R4-2201957 |
RF requirements for further enhancements on MIMO |
Huawei, HiSilicon |
6.19.2.2 |
Impact of MPE enhancements |
|
R4-2200301 |
On per beam based P-MPR reporting in FeMIMO |
Apple |
R4-2200592 |
Discussion on Impact of MPE enhancements |
ZTE Corporation |
R4-2200963 |
Further discussion on impact of MPE requirements |
vivo |
6.19.2.3 |
SRS related impact |
|
R4-2200342 |
Two sets of SRS sets and GP needed in between |
Qualcomm Incorporated |
6.19.3 |
RRM core requirements |
|
R4-2202570 |
Email discussion summary for [101-bis-e][219] NR_feMIMO_RRM |
Moderator (Samsung) |
R4-2202736 |
Email discussion summary for [101-bis-e][219] NR_feMIMO_RRM |
Moderator (Samsung) |
6.19.3.1 |
Unified TCI for DL and UL |
|
R4-2200182 |
Discussion on unified TCI for DL and UL in R17 feMIMO |
MediaTek Inc. |
R4-2200277 |
Discussion on RRM requirements for Unified TCI |
Apple |
R4-2200593 |
Discussion on Unified TCI for DL and UL |
ZTE Corporation |
R4-2200602 |
Discussion on RRM requirements for unified TCI in R17 feMIMO |
vivo |
R4-2200642 |
Discussion on unified TCI |
CMCC |
R4-2200649 |
Discussion on requirements of unified TCI for DL and UL |
Nokia, Nokia Shanghai Bell |
R4-2200787 |
Discussion on Unified TCI state in NR FeMIMO |
Intel Corporation |
R4-2201363 |
Unified TCI in FeMIMO |
Samsung |
R4-2201384 |
RRM requirements of unified TCI state for FeMIMO |
Ericsson |
R4-2201616 |
Discussion on RRM requirements related to unified TCI framework for NR FeMIMO |
Huawei, Hisilicon |
R4-2202666 |
WF on RRM impact on unified TCI in FeMIMO |
Samsung |
R4-2202667 |
WF on FeMIMO RRM requirements for inter-cell beam management |
Samsung |
R4-2202668 |
WF on other RRM requirements for FeMIMO |
Huawei |
R4-2202669 |
Reply LS on L1-RSRP measurement behaviour when SSBs associated with different PCIs |
vivo |
R4-2202770 |
WF on FeMIMO RRM requirements for inter-cell beam management |
Samsung |
R4-2202771 |
Reply LS on L1-RSRP measurement behaviour when SSBs associated with different PCIs overlap |
vivo |
R4-2202772 |
WF on FeMIMO RRM requirements for inter-cell beam management |
Samsun g |
6.19.3.2 |
Inter-cell beam management |
|
R4-2200183 |
Discussion on inter cell beam management in R17 feMIMO |
MediaTek Inc. |
R4-2200278 |
Discussion on RRM requirements for inter-cell beam management |
Apple |
R4-2200594 |
Discussion on RRM requirements for inter-cell beam management |
ZTE Corporation |
R4-2200603 |
Discussion on RRM requirements for inter-cell L1 beam measurements in R17 feMIMO |
vivo |
R4-2200643 |
Discussion on inter-cell beam management |
CMCC |
R4-2200650 |
Discussion on requirements of inter-cell beam management |
Nokia, Nokia Shanghai Bell |
R4-2200788 |
Discussion on inter-cell beam management in NR FeMIMO |
Intel Corporation |
R4-2201385 |
RRM requirements of inter-cell BM in FeMIMO |
Ericsson |
R4-2201617 |
Discussion on inter-cell beam management requirements for NR FeMIMO |
Huawei, Hisilicon |
R4-2201960 |
Inter-cell beam management in FeMIMO |
Samsung |
6.19.3.3 |
Others |
|
R4-2200184 |
Discussion on general and RRM requirements impacts in R17 feMIMO |
MediaTek Inc. |
R4-2200279 |
Discussion on other RRM requirements for FeMIMO |
Apple |
R4-2200535 |
Discussion on remaining issues in FeMIMO |
Intel Corporation |
R4-2200536 |
DraftCR on TCI chain update for Rel-17 NR FeMIMO |
Intel Corporation |
R4-2200604 |
Discussion on other RRM impacts in R17 feMIMO |
vivo |
R4-2200651 |
Discussion on other items of Rel-17 feMIMO RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2201387 |
Discussion on FeMIMO other open issues |
Ericsson |
R4-2201618 |
Discussion on other RRM requirements for NR FeMIMO |
Huawei, Hisilicon |
R4-2202750 |
DraftCR on TCI chain update for Rel-17 NR FeMIMO |
Intel |
6.19.4 |
UE Demodulation and CSI requirements |
|
R4-2200280 |
On scope of demod requirements for FeMIMO |
Apple |
R4-2200365 |
Views on Rel-17 HST-SFN scheme 1 |
NTT DOCOMO, INC. |
R4-2200522 |
Discussion on demodulation performance requirements definition for Rel-17 NR feMIMO |
Intel Corporation |
R4-2200644 |
Discussion on demodulation requirements for enhancement to support HST-SFN |
CMCC |
R4-2200767 |
Overview and work plan on performance requirements of Rel-17 FeMIMO WI |
Samsung |
R4-2201014 |
Discussion on UE FeMIMO demod |
Huawei,HiSilicon |
R4-2201421 |
Discussion on UE demodulation and CSI requirement for FeMIMO |
Ericsson |
R4-2201841 |
Views on FeMIMO Tests |
Qualcomm CDMA Technologies |
R4-2201922 |
On UE Demodulation and CSI requirements for feMIMO |
Nokia, Nokia Shanghai Bell |
R4-2202976 |
Email discussion summary for [101-bis-e][320] NR_FeMIMO_Demod_NWM |
Moderator (Samsung) |
R4-2203090 |
WF on general and CSI requirement for Rel-17 FeMIMO |
Samsung |
R4-2203091 |
WF on demodulation requirement for Enhancement on HST-SFN deployment |
Intel Corporation |
R4-2203092 |
WF on demodulation requirement for Enhancement on Multi-TRP |
Huawei |
R4-2203118 |
Email discussion summary for [101-bis-e][320] NR_FeMIMO_Demod_NWM |
Moderator (Samsung) |
6.20.1 |
General |
|
R4-2200407 |
On NR RedCap general BS demodulation performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2202232 |
Email discussion summary for [101-bis-e][132] NR_RedCap |
Moderator (Ericsson) |
R4-2202332 |
Email discussion summary for [101-bis-e][132] NR_RedCap |
Moderator (Ericsson) |
R4-2202371 |
WF on the RedCap RF |
Ericsson |
R4-2202372 |
CR on RedCap UE FR1-TX |
Ericsson |
6.20.2.1 |
FR1 |
|
R4-2201250 |
Draft CR for 38.101-1 to introduce RF requirements for RedCap UE |
Huawei, HiSilicon, CMCC, OPPO, CBN |
R4-2201988 |
RedCap general UE RF requirements aspects |
MediaTek (Chengdu) Inc. |
6.20.2.1.1 |
Tx requirements (power class) |
|
R4-2200496 |
RedCap UL Architecture and power class |
Skyworks Solutions Inc. |
R4-2201279 |
R17 FR1 Redcap UE |
OPPO |
R4-2201301 |
Discussion on Tx requirements for FR1 Redcap UE |
Xiaomi |
R4-2201345 |
On FR1 Redcap UE 2Tx |
ZTE Corporation |
R4-2201709 |
CR on RedCap UE FR1-TX |
Ericsson |
6.20.2.1.2 |
Rx requirements (REFSENS, etc) |
|
R4-2200442 |
RedCap UE HD-FDD REFSENS requirements |
Apple |
R4-2200472 |
Considerations on REFSENS for RedCap FR1 |
Sony |
R4-2201248 |
Discussion on FR1 REFSENS requirements for RedCap UE |
Huawei, HiSilicon |
R4-2201344 |
Further discussion on FR1 RedCap related requirements |
ZTE Corporation |
R4-2201710 |
CR on RedCap UE FR1-RX |
Ericsson |
R4-2202373 |
Draft CR for 38.101-1 to introduce RF requirements for RedCap UE |
Huawei, HiSilicon, CMCC, OPPO, CBN |
6.20.2.2 |
FR2 |
|
R4-2201249 |
Discussion on FR2 RF requirements for RedCap UE |
Huawei, HiSilicon |
6.20.2.2.1 |
Tx requirements (power class, UE type) |
|
R4-2200473 |
Considerations on RF architecture for RedCap FR2 |
Sony |
R4-2200571 |
View on FR2 RedCap |
MediaTek Beijing Inc. |
R4-2200978 |
Discussion on FR2 RedCap Tx requirements |
vivo |
R4-2201302 |
Discussion on Tx requirements for FR2 Redcap UE |
Xiaomi |
R4-2201346 |
Discussion on FR2 RedCap UE |
ZTE Corporation |
R4-2201713 |
RF impact On FR2 RedCap |
Ericsson |
R4-2201972 |
On Redcap FR2-1 UE Tx RF assumptions |
Qualcomm Incorporated |
6.20.2.2.2 |
Rx requirements |
|
R4-2200979 |
Discussion on FR2 RedCap Rx requirements |
vivo |
R4-2201303 |
Discussion on Rx requirements for FR2 Redcap UE |
Xiaomi |
R4-2201712 |
On single polarization receiving on FR2 RedCap UE |
Ericsson |
R4-2201971 |
On Redcap FR2-1 UE Rx RF assumptions |
Qualcomm Incorporated |
6.20.2.3 |
Others |
|
R4-2201711 |
RedCap FR1 Operating band n79 |
Ericsson |
6.20.3 |
RRM core requirements |
|
R4-2201857 |
Updated WI work plan for RedCap for RRM |
Ericsson |
R4-2202571 |
Email discussion summary for [101-bis-e][220] NR_redcap_RRM_1 |
Moderator (Ericsson) |
6.20.3.1.1 |
General |
|
R4-2200392 |
On general aspects on complexity reduction of Redcap |
vivo |
R4-2200692 |
Further discussion on general requirements on Redcap UE |
Xiaomi |
R4-2200808 |
On general requirements for RedCap UE |
CMCC |
R4-2201183 |
Discussion on general RRM requirements impacts for RedCap UE |
Huawei, Hisilicon |
R4-2201394 |
reply LS on capability related assumptions for RedCap |
ZTE Corporation |
R4-2201397 |
Discussions on general RRM aspects for RedCap UEs |
ZTE Corporation |
R4-2201773 |
General discussion UE capability and scheduling availability |
MediaTek inc. |
R4-2201858 |
Discussions on general requirements for RedCap |
Ericsson |
R4-2201979 |
Discussion on PBCH simulation assumptions for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2202670 |
WF on RedCap RRM requirements |
Ericsson |
R4-2202671 |
LS on RSRP based thresholds for RedCap UE with 1 Rx |
Ericsson |
R4-2202718 |
Updated WI work plan for RedCap for RRM |
Ericsson |
R4-2202761 |
Reply LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE |
vivo |
R4-2202762 |
Draft Big CR: RRM requirements for Rel-17 NR RedCap |
Ericsson |
R4-2202763 |
Draft Big CR: RRM requirements for Rel-17 NR RedCap |
Ericsson |
R4-2202773 |
Reply LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE |
vivo |
R4-2202774 |
WF on the use of NCD-SSB or CSI-RS for RedCap UE |
CMCC |
6.20.3.1.2 |
Mobility requirements |
|
R4-2200292 |
Discussion on mobility requirement for RedCap |
Apple |
R4-2200393 |
On mobility requirements for Redcap |
vivo |
R4-2200809 |
On mobility requirements for RedCap UE |
CMCC |
R4-2200871 |
Discussion on mobility requirements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2201184 |
Discussion on UE mobility requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2201388 |
Requirements under RRC Connected mode for RedCap UEs |
ZTE Corporation |
R4-2201774 |
Discussion on mobility requirements |
MediaTek inc. |
R4-2201859 |
Discussions on RedCap mobility requirements |
Ericsson |
6.20.3.1.3 |
Timing requirements |
|
R4-2200810 |
On timings requirements for RedCap UE |
CMCC |
R4-2201185 |
Discussion on UE timing requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2201389 |
Timing requirements for RedCap UEs |
ZTE Corporation |
R4-2201775 |
UE complexity reduction impact on timing requirements |
MediaTek inc. |
R4-2201860 |
On UE transmit timing requirements in Redcap |
Ericsson |
6.20.3.1.4 |
Signalling characteristics |
|
R4-2200293 |
Discussion on signalling characteristics for RedCap |
Apple |
R4-2200394 |
On signalling characteristics for Redcap |
vivo |
R4-2200399 |
Simulation results for RLM and BFD |
vivo |
R4-2200400 |
Simulation results for PDCCH RLM and BFD |
vivo |
R4-2200811 |
On Signalling characteristics requirements for RedCap UE |
CMCC |
R4-2200867 |
Simulation Results: RLM for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2200868 |
Discussion on hypothetical PDCCH parameters for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2201145 |
RRM impact from UE complexity reduction for Redcap UE - signaling characteristics |
OPPO |
R4-2201186 |
Discussion on signaling characteristics due to UE complexity reduction |
Huawei, Hisilicon |
R4-2201187 |
Simulation results for RLM and BFD due to complexity reduction for RedCap UE |
Huawei, Hisilicon |
R4-2201390 |
On Signalling characteristics of RedCap UEs |
ZTE Corporation |
R4-2201776 |
Discussion on RLM and BFD in RedCap |
MediaTek inc. |
R4-2201861 |
Discussions on RedCap signaling characteristics |
Ericsson |
R4-2202030 |
Impact of UE complexity reduction impact on signalling characteristics |
Qualcomm Incorporated |
6.20.3.1.5 |
Measurement procedure |
|
R4-2200294 |
Discussion on cell identification and measurement for RedCap |
Apple |
R4-2200395 |
On measurement procedure for Redcap |
vivo |
R4-2200401 |
Simulation results for cell detection, PBCH detection, SSB measurement and L1 RSRP measurement |
vivo |
R4-2200812 |
On Measurement procedure for RedCap UE |
CMCC |
R4-2200869 |
Discussion on measurement procedures for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2200870 |
Simulation Results: cell detection performance for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2201146 |
RRM impact from UE complexity reduction for Redcap UE - measurement requirements |
OPPO |
R4-2201188 |
Discussion on measurement requirements due to UE complexity reduction |
Huawei, Hisilicon |
R4-2201189 |
Simulation results for cell detection, L3 measurement and L1 RSRP measurement |
Huawei, Hisilicon |
R4-2201391 |
Measurement procedure of RedCap UEs |
ZTE Corporation |
R4-2201777 |
Simulation performance results for RedCap |
MediaTek inc. |
R4-2201862 |
Discussions on RedCap measurement procedure |
Ericsson |
R4-2202031 |
Impact of UE complexity reduction on measurement procedures |
Qualcomm Incorporated |
6.20.3.2 |
Extended DRX enhancements |
|
R4-2200295 |
Discussion on RRM requirement with eDRX for RedCap |
Apple |
R4-2200396 |
On Redcap eDRX enhancement |
vivo |
R4-2200690 |
Further discussion on RRM requirements for extended DRX enhancements for RedCap |
Xiaomi |
R4-2200813 |
On Extended DRX cycle for RedCap UE |
CMCC |
R4-2200866 |
Discussion on eDRX enhancements for RedCap |
Nokia, Nokia Shanghai Bell |
R4-2201147 |
Extended DRX enhancements for Redcap UE |
OPPO |
R4-2201190 |
Discussion on Extended DRX enhancements for RedCap UE |
Huawei, Hisilicon |
R4-2201392 |
On extended DRX enhancements for RedCap |
ZTE Corporation |
R4-2201778 |
Extended DRX in IDLE mode and INACTIVE mode |
MediaTek inc. |
R4-2201863 |
Discussions on eDRX requirements for RedCap |
Ericsson |
R4-2202572 |
Email discussion summary for [101-bis-e][221] NR_redcap_RRM_2 |
Moderator (Vivo) |
R4-2202672 |
WF on eDRX and RRM measurement relaxations requirements for Redcap UE |
vivo |
R4-2202673 |
WF on the use of NCD-SSB or CSI-RS for RedCap UE |
CMCC |
R4-2202674 |
Reply LS on use of NCD-SSB for RedCap UE |
ZTE |
R4-2202675 |
LS on RRM relaxation for Redcap |
vivo |
R4-2202676 |
Reply LS on UE capabilities for RedCap from RRM perspective |
Ericsson |
R4-2202737 |
Email discussion summary for [101-bis-e][220] NR_redcap_RRM_1 |
Moderator (Ericsson) |
R4-2202738 |
Email discussion summary for [101-bis-e][221] NR_redcap_RRM_2 |
Moderator (Vivo) |
6.20.3.3 |
RRM measurement relaxations |
|
R4-2200296 |
Discussion on RRM relaxation requirement for RedCap |
Apple |
R4-2200397 |
On Redcap RRM relaxation |
vivo |
R4-2200691 |
Further discussion on RRM measurement relaxations for RedCap UE |
Xiaomi |
R4-2200814 |
On RRM measurement relaxation for RedCap UE |
CMCC |
R4-2201148 |
RRM measurement relaxations for RedCap UE |
OPPO |
R4-2201191 |
Discussion on RRM measurement relaxations for RedCap UE |
Huawei, Hisilicon |
R4-2201393 |
Discussions on RRM measurement relaxations for RedCap UEs |
ZTE Corporation |
R4-2201779 |
RRM measurements relaxation for stationary criterion |
MediaTek inc. |
R4-2201864 |
Discussions on RRM measurement relaxations |
Ericsson |
R4-2201980 |
On RRM measurement relaxation for neighbouring cells |
Nokia, Nokia Shanghai Bell |
R4-2202032 |
RRM relaxations enhancements for RedCap UE |
Qualcomm Incorporated |
6.20.3.4 |
Others |
|
R4-2200398 |
On NCD-SSB or CSI-RS in DL BWPs for RedCap UE |
vivo |
R4-2200815 |
Reply LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE |
CMCC |
R4-2201192 |
Discussion on NCD-SSB and CSI-RS |
Huawei, Hisilicon |
R4-2201395 |
Reply LS on use of NCD-SSB for RedCap UE |
ZTE Corporation |
R4-2201396 |
reply LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE |
ZTE Corporation |
R4-2201760 |
On capability and NCD-SSB design for RedCap RRM |
Apple |
R4-2201780 |
Discussion on the use of NCD-SSB |
MediaTek inc. |
R4-2201865 |
RRM Discussions on RedCap UE capabilities |
Ericsson |
R4-2201981 |
Discussion on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE |
Nokia, Nokia Shanghai Bell |
6.20.4 |
UE demodulation and CSI requirements |
|
R4-2200281 |
On impact to demod requirements for Reduced capability devices in NR |
Apple |
R4-2200382 |
Views on UE demodulation requirements for RedCap |
MediaTek inc. |
R4-2200406 |
On NR RedCap general UE demodulation and CSI performance requirements |
Nokia, Nokia Shanghai Bell |
R4-2200816 |
On UE demodulation and CSI requirements for RedCap UE |
CMCC |
R4-2200994 |
Discussion on UE demodulation and CSI requirements for RedCap |
Huawei,HiSilicon |
R4-2201435 |
Work plan for UE demodulation requirements for RedCap |
Ericsson |
R4-2201436 |
UE demodulation and CSI reporting requirements for RedCap |
Ericsson |
R4-2201605 |
Discussion on scope of UE demodulation and CSI requirements for reduced capability NR devices |
Intel Corporation |
R4-2201720 |
Introduction of RedCap Demodulation Requirements |
Qualcomm Incorporated |
R4-2202977 |
Email discussion summary for [101-bis-e][321] NR_RedCap_Demod_NWM |
Moderator (Ericsson) |
R4-2203032 |
WF on RedCap demodulation and CQI reporting requirements |
Ericsson |
R4-2203119 |
Email discussion summary for [101-bis-e][321] NR_RedCap_Demod_NWM |
Moderator (Ericsson) |
6.21.1 |
General |
|
R4-2200385 |
Work plan for Multi-SIM devices for LTE/NR |
vivo |
R4-2202015 |
Work split on RRM core requirements for postioning |
Ericsson |
R4-2202016 |
Big DraftCR on Positioning Enhancement |
Ericsson |
R4-2202573 |
Email discussion summary for [101-bis-e][222] NR_pos_enh_1 |
Moderator (Ericsson) |
R4-2202677 |
WF on NR Positioning Enhancements (Part 1) |
Ericsson |
R4-2202678 |
LS reply on lower Rx beam sweeping factor for latency improvement |
CATT |
R4-2202679 |
LS reply on condition of PRS measurement outside the MG |
Vivo |
R4-2202680 |
LS on SRS for multi-RTT positioning |
Huawei, HiSilicon |
R4-2202681 |
LS reply on definition of DL PRS path RSRP |
Nokia |
R4-2202682 |
LS reply on UL SRS-RSRPP definition |
Ericsson |
R4-2202683 |
Big DraftCR on Positioning Enhancement |
Ericsson |
R4-2202739 |
Email discussion summary for [101-bis-e][222] NR_pos_enh_1 |
Moderator (Ericsson) |
R4-2202775 |
LS reply on definition of DL PRS path RSRP |
Nokia |
R4-2202776 |
WF on NR Positioning Enhancements (Part 1) |
Ericsson |
R4-2202780 |
LS reply on definition of DL PRS path RSRP |
Nokia |
6.21.2.1 |
UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
|
R4-2200118 |
Discussion on UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
CATT |
R4-2200119 |
Reply LS on the reporting of the Tx TEG association information |
CATT |
R4-2200540 |
Discussion on timing mitigating for NR positioning enhancement |
Intel Corporation |
R4-2200668 |
Further discussion on timing delay error mitigation |
vivo |
R4-2200757 |
On UE Rx/Tx timing error mitigation |
Qualcomm Incorporated |
R4-2201163 |
Discussion on UE Rx/Tx and/or gNB Rx/Tx timing delay mitigation |
OPPO |
R4-2201293 |
Impact of RX/TX TEG on UE requirements |
Ericsson Inc. |
R4-2201398 |
UE RxTx and gNB RxTx timing delay mitigation |
ZTE Corporation |
R4-2201636 |
Discussion on timing error mitigation for positioning |
Huawei, Hisilicon |
R4-2201668 |
Impact of RX/TX TEG on UE requirements |
Ericsson |
R4-2201982 |
Discussion on timing error mitigation for NR positioning |
Nokia, Nokia Shanghai Bell |
R4-2202574 |
Email discussion summary for [101-bis-e][223] NR_pos_enh_2 |
Moderator (CATT) |
R4-2202740 |
Email discussion summary for [101-bis-e][223] NR_pos_enh_2 |
Moderator (CATT) |
6.21.2.2 |
Latency reduction of positioning measurement |
|
R4-2200120 |
Discussion on latency reduction of positioning measurement |
CATT |
R4-2200541 |
Discussion on latency reduction for NR positioning enhancement |
Intel Corporation |
R4-2200542 |
Simulation results summary for conditions with less PRS measurement samples |
Intel Corporation |
R4-2200637 |
Discussion on latency reduction of positioning measurement |
CMCC |
R4-2200645 |
Discussion on latency reduction of positioning measurement |
Nokia, Nokia Shanghai Bell |
R4-2200646 |
Discussion on PRS measurement performance with reduced sample |
Nokia, Nokia Shanghai Bell |
R4-2200664 |
Simulation results for PRS measurement with reduced sample |
vivo |
R4-2200665 |
Further discussion on latency reduction of positioning measurement |
vivo |
R4-2200667 |
Reply LS on the condition of PRS measurement outside the MG |
vivo |
R4-2200758 |
Simulation results with reduced number of PRS samples |
Qualcomm Incorporated |
R4-2200759 |
On latency reduction of NR positioning measurements |
Qualcomm Incorporated |
R4-2201164 |
Discussion on latency reduction of positioning measurements |
OPPO |
R4-2201294 |
Link level simulation results for latency reduction for UE measurements |
Ericsson Inc. |
R4-2201306 |
On latency reduction for positioning measurement |
Ericsson Inc. |
R4-2201370 |
Draft CR to 38.133 Introducing requirements for latency reduction of positioning measurement |
vivo |
R4-2201399 |
Discussions on latency reduction of positioning measurement |
ZTE Corporation |
R4-2201637 |
Simulation results for reduced sample number for PRS measurement |
Huawei, Hisilicon |
R4-2201638 |
On latency reduction for positioning measurement |
Huawei, Hisilicon |
R4-2201639 |
CR on latency reduction of positioning measurements |
Huawei, Hisilicon |
R4-2201669 |
Link level simulation results for latency reduction for UE measurements |
Ericsson |
R4-2201670 |
On latency reduction for positioning measurement |
Ericsson |
6.21.2.3 |
Measurement in RRC_INACTIVE state |
|
R4-2200121 |
Discussion on measurement in RRC_INACTIVE state |
CATT |
R4-2200543 |
Discussion on measurements in RRC_INACTIVE for NR positioning enhancement |
Intel Corporation |
R4-2200636 |
Discussion on positioning measurement in RRC_INACTIVE state |
CMCC |
R4-2200760 |
On NR positioning measurements in RRC_INACTIVE |
Qualcomm Incorporated |
R4-2201165 |
Discussion on PRS measurements in RRC_INACTIVE state |
OPPO |
R4-2201364 |
Further discussion on measurement in RRC_INACTIVE state |
vivo |
R4-2201400 |
Positioning measurements in RRC_INACTIVE state |
ZTE Corporation |
R4-2201640 |
Discussion on PRS measurement in RRC_INACTIVE |
Huawei, Hisilicon |
R4-2201641 |
CR on positioning measurements in RRC Inactive state |
Huawei, Hisilicon |
R4-2201983 |
Discussion on measurement in RRC_INACTIVE state |
Nokia, Nokia Shanghai Bell |
R4-2202017 |
Analysis PRS measurement requirements in RRC inactive state |
Ericsson |
R4-2202684 |
WF on NR Positioning Enhancements (Part 2) |
CATT |
R4-2202685 |
Reply LS on reporting of the Tx TEG association information |
Huawei |
R4-2202686 |
LS on DRX cycle used in PRS measurement in RRC_INACTIVE state |
Qualcomm |
R4-2202687 |
LS on the applicability of PRS processing window in RRC_INACTIVE state |
CATT |
6.21.2.4 |
Impact on existing UE positioning and RRM requirements |
|
R4-2200122 |
Discussion on impact on existing UE positioning and RRM requirements |
CATT |
R4-2200647 |
Discussion on Impact on NR positioning RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2200663 |
Further discussion on impact to existing UE positioning and RRM requirements |
vivo |
R4-2201166 |
Impacts of SRS antenna port switching on positioning |
OPPO |
R4-2201307 |
Impact of enhanced positioning on existing RRM |
Ericsson Inc. |
R4-2201401 |
Impact on existing UE positioning and RRM requirements |
ZTE Corporation |
R4-2201642 |
Discussion on RAN4 specific enhancements for positioning |
Huawei, Hisilicon |
R4-2201671 |
Impact of enhanced positioning on existing RRM |
Ericsson |
R4-2202018 |
Impact of RRM on positioning requirements |
Ericsson |
6.21.2.6 |
Others |
|
R4-2200123 |
Reply LS on the condition of PRS measurement outside the MG |
CATT |
R4-2200124 |
Reply LS on lower Rx beam sweeping factor for latency improvement |
CATT |
R4-2200648 |
Discussion on other items of NR ePos requirements |
Nokia, Nokia Shanghai Bell |
R4-2200662 |
Further discussion on First path PRS-RSRP requirments |
vivo |
R4-2200666 |
Link level simulation assumption for first path PRS-RSRP measurement |
vivo |
R4-2201167 |
Other issues of positioning enhancements for NR |
OPPO |
R4-2201309 |
LS response on SRS on UL SRS-RSRPP definition |
Ericsson Inc. |
R4-2201402 |
on PRS measurement outside the measurement gap |
ZTE Corporation |
R4-2201643 |
Discussion on path RSRP |
Huawei, Hisilicon |
R4-2201672 |
LS response on SRS on UL SRS-RSRPP definition |
Ericsson |
6.22 |
Multi-Radio Dual-Connectivity enhancements |
|
R4-2202575 |
Email discussion summary for [101-bis-e][224] LTE_NR_DC_enh2 |
Moderator (Huawei) |
R4-2202741 |
Email discussion summary for [101-bis-e][224] LTE_NR_DC_enh2 |
Moderator (Huawei) |
6.22.2.1 |
Efficient activation/de-activation mechanism for SCells |
|
R4-2200063 |
Discussion on efficient activation/de-activation mechanism for SCell |
MediaTek (Shenzhen) Inc. |
R4-2200248 |
On efficient activation/de-activation mechanism for SCells |
Apple |
R4-2200403 |
Draft CR for Interruption due to A-TRS based fast SCell activation |
vivo |
R4-2200423 |
Efficient activation and deactivation mechanism for SCells |
Qualcomm Incorporated |
R4-2201149 |
Discussion on efficient activation/de-activation mechanism for Scells |
OPPO |
R4-2201179 |
Discussion on efficient activation/de-activation mechanism for Scells |
Huawei, Hisilicon |
R4-2201180 |
Draft CR on fast activation delay |
Huawei, Hisilicon |
R4-2201690 |
Discussion on efficient activation/de-activation mechanism for Scells |
Nokia, Nokia Shanghai Bell |
R4-2201886 |
On efficient (de)activation of Scell |
Ericsson |
R4-2202688 |
WF on R17 further Multi-RAT Dual-Connectivity enhancements |
Huawei, HiSilicon |
R4-2202689 |
Draft Big CR on R17 further Multi-RAT Dual-Connectivity enhancements |
Huawei, HiSilicon |
R4-2202690 |
Draft CR for Interruption due to A-TRS based fast SCell activation |
vivo |
R4-2202691 |
Draft CR on fast activation delay |
Huawei |
R4-2202692 |
CR on interruptions due to SCG activation/deactivation |
Apple |
R4-2202693 |
CR on TS36.133 for interruptions due to SCG activation/deactivation |
Apple |
R4-2202694 |
DraftCR on interruptions due to RRM measurements on deactivated SCG |
Intel |
R4-2202695 |
Interruptions requirments due to RLM/BFD on deactivated SCG |
Ericsson |
R4-2202696 |
Draft CR to 38133 on SCG Activation and deactivation delay |
OPPO |
R4-2202697 |
Draft CR to 36133 on SCG Activation and deactivation delay |
OPPO |
R4-2202698 |
LS on Measurement requirement for deactivated SCG |
Ericsson |
R4-2202699 |
Draft CR on 38.133 for Conditional PSCell addition delay |
MediaTek |
R4-2202700 |
Draft Big CR on R17 further Multi-RAT Dual-Connectivity enhancements |
Huawei, HiSilicon |
R4-2202777 |
LS on Measurement requirement for deactivated SCG |
Ericsson |
R4-2202778 |
Interruptions requirments due to RLM/BFD on deactivated SCG |
Ericsson |
R4-2202781 |
LS on Measurement requirement for deactivated SCG |
Ericsson |
6.22.2.2 |
Efficient activation/de-activation mechanism for one SCG |
|
R4-2200064 |
Discussion on efficient activation/de-activation mechanism for one SCG |
MediaTek (Shenzhen) Inc. |
R4-2200249 |
On efficient activation/de-activation mechanism for one SCG |
Apple |
R4-2200250 |
CR on interruptions due to SCG activation/deactivation |
Apple |
R4-2200424 |
Efficient activation and deactivation mechanism for one SCG |
Qualcomm Incorporated |
R4-2200526 |
Discussion on efficient activation for one SCG |
Intel Corporation |
R4-2200527 |
DraftCR on interruptions due to RRM measurements on deactivated SCG |
Intel Corporation |
R4-2200652 |
Further discussion on efficient activation deactivation mechanism for one SCG |
vivo |
R4-2201150 |
Discussion on efficient activation/de-activation mechanism for one SCG |
OPPO |
R4-2201181 |
Discussion on efficient activation/de-activation mechanism for one SCG |
Huawei, Hisilicon |
R4-2201691 |
Views on efficient activation/de-activation mechanism for one SCG |
Nokia, Nokia Shanghai Bell |
R4-2201761 |
CR on TS36.133 for interruptions due to SCG activation/deactivation |
Apple |
R4-2201887 |
On efficient (de)activation of SCG |
Ericsson |
R4-2201890 |
Interruptions requirments due to RLM/BFD on deactivated SCG |
Ericsson |
6.22.2.3 |
Conditional PSCell change and addition |
|
R4-2200065 |
Discussion on conditional PSCell addition |
MediaTek (Shenzhen) Inc. |
R4-2200066 |
Draft CR on 38.133 for Conditional PSCell addition delay |
MediaTek (Shenzhen) Inc. |
R4-2200251 |
On conditional PSCell change and addition |
Apple |
R4-2200653 |
Further discussion on conditional PSCell change and addition |
vivo |
R4-2201151 |
Discussion on conditional PSCell change and addition |
OPPO |
R4-2201182 |
Discussion on conditional PSCell change and addition |
Huawei, Hisilicon |
R4-2201692 |
Conditional PSCell change and addition |
Nokia, Nokia Shanghai Bell |
R4-2201888 |
On conditional Pscell change addition |
Ericsson |
6.22.2.4 |
Others |
|
R4-2201152 |
Draft CR to 38133 on SCG Activation and deactivation delay |
OPPO |
R4-2201153 |
Draft CR to 36133 on SCG Activation and deactivation delay |
OPPO |
R4-2201889 |
LS on Measurement requirement for deactivated SCG |
Ericsson |
6.23 |
Enhanced IIoT and URLLC support |
|
R4-2202576 |
Email discussion summary for [101-bis-e][225] NR_IIOT_URLLC_enh |
Moderator (Nokia) |
R4-2202742 |
Email discussion summary for [101-bis-e][225] NR_IIOT_URLLC_enh |
Moderator (Nokia) |
6.23.1 |
General |
|
R4-2202779 |
WF on NR_IIOT_URLLC_enh RRM requirements |
Nokia, Nokia Shanghai Bell |
R4-2202782 |
WF on NR_IIOT_URLLC_enh RRM requirements |
Nokia, Nokia Shanghai Bell |
6.23.2.1 |
Propagation delay compensation enhancements |
|
R4-2201168 |
Discussion on propagation delay compensation enhancements |
OPPO |
R4-2201368 |
Further discussion on propagation delay compensation enhancements |
vivo |
R4-2201584 |
Propagation Delay Compensation Enhancements for Time Synchronization |
Ericsson |
R4-2201633 |
On RRM requirements for PDC enhancements |
Huawei, Hisilicon |
R4-2201634 |
CR on requirements for UE Rx-Tx measurement for PDC |
Huawei, Hisilicon |
R4-2201721 |
Discussion of RRM Requirements for Propagation Delay Compensation Enhancements |
Nokia |
R4-2201723 |
Discussion of RRM Requirements for Propagation Delay Compensation Enhancements |
Nokia |
R4-2201781 |
RTT-based PDC enhancements in URLLC |
MediaTek inc. |
R4-2202701 |
WF on NR_IIOT_URLLC_enh_RRM |
Nokia, Nokia Shanghai Bell |
R4-2202702 |
Reply LS on TA-based propagation delay compensation |
Nokia |
R4-2202703 |
Correction to reference point defintion for UE timing in TS 38.133 |
Ericsson, Intel, Huawei, HiSilicon |
R4-2202704 |
DraftCR to clarify timing reference point for UE UL timing test cases |
Intel |
R4-2202705 |
CR on requirements for UE Rx-Tx measurement for PDC |
Huawei, Hisilicon |
6.23.2.2 |
Reference point for Te requirements |
|
R4-2200528 |
DraftCR to clarify timing reference point for UE UL timing test cases |
Intel Corporation |
R4-2201369 |
Further discussion on reference point for Te requirements |
vivo |
R4-2201635 |
On reference point for Te requirements |
Huawei, Hisilicon |
R4-2201673 |
Discussion on reference point for Te requirements |
Intel Corporation |
R4-2201722 |
Further discussion on the reference point for UE transmit timing requirement |
Nokia |
R4-2201782 |
Reference point for Te requirements |
MediaTek inc. |
R4-2202013 |
LS response on UE transmit timing error |
Ericsson |
R4-2202014 |
Correction to reference point defintion for UE timing in TS 38.133 |
Ericsson, Intel, Huawei, HiSilicon |
6.24 |
NR Sidelink Relay |
|
R4-2202577 |
Email discussion summary for [101-bis-e][226] NR_SL_relay |
Moderator (OPPO) |
R4-2202743 |
Email discussion summary for [101-bis-e][226] NR_SL_relay |
Moderator (OPPO) |
6.24.1 |
General |
|
R4-2201154 |
CR to 38133 on measurement requirements for Selection/reselection of relay UE |
OPPO |
R4-2202748 |
Draft Big CR on RRM Core requirements for Rel-17 NR SL Relay (TS 38.133) |
OPPO |
6.24.2 |
RRM core requirements |
|
R4-2200324 |
On NR SL relay RRM Requirement |
Qualcomm, Inc. |
R4-2200330 |
CR: SL discovery signal intra-frequency measurement accuracy requirements |
Qualcomm, Inc. |
R4-2201155 |
RRM requirements for SL relay (re)selection |
OPPO |
R4-2201619 |
Discussion on RRM requirements for R17 NR sidelink relay |
Huawei, Hisilicon |
R4-2201620 |
DraftCR on interruption requirements for NR SL relay |
Huawei, Hisilicon |
R4-2201872 |
RRM requirements for Rel-17 SL relay operation |
Ericsson |
R4-2202706 |
WF on NR SL relay RRM |
OPPO |
R4-2202707 |
CR to 38133 on measurement requirements for Selection/reselection of relay UE |
OPPO |
R4-2202708 |
DraftCR on interruption requirements for NR SL relay |
Huawei |
R4-2202709 |
CR: SL discovery signal intra-frequency measurement accuracy requirements |
Qualcomm |
6.25 |
NR small data transmissions in INACTIVE state |
|
R4-2202578 |
Email discussion summary for [101-bis-e][227] NR_SmallData_INACTIVE |
Moderator (ZTE) |
R4-2202744 |
Email discussion summary for [101-bis-e][227] NR_SmallData_INACTIVE |
Moderator (ZTE) |
6.25.1 |
General and work plan |
|
R4-2200918 |
On BS demodulation performance requirements for CG-SDT |
Nokia, Nokia Shanghai Bell |
6.25.2 |
RRM core requirements |
|
R4-2200300 |
On RRM requirement for CG-SDT |
Apple |
R4-2200417 |
RRM requirements for NR-SDT |
Qualcomm Incorporated |
R4-2200919 |
TA validation requirements for CG-SDT |
Nokia, Nokia Shanghai Bell |
R4-2200920 |
Draft CR TA validation for Small Data Transmissions |
Nokia, Nokia Shanghai Bell |
R4-2201644 |
Discussion on remaining issues for SDT RRM |
Huawei, Hisilicon |
R4-2201645 |
CR on UL timing requirements for SDT |
Huawei, Hisilicon |
R4-2201792 |
Draft big CR for SDT RRM requirements |
ZTE Wistron Telecom AB |
R4-2201793 |
Further discussion on RRM requirements for SDT |
ZTE Wistron Telecom AB |
R4-2201853 |
RRM requirements for SDT |
MediaTek Inc. |
R4-2201869 |
Discussions on RRM requirements for Small Data Transmissions |
Ericsson |
R4-2201870 |
Draft CR to TS 38.133: Requirements on UE synchoronization for SDT |
Ericsson |
R4-2202710 |
WF on RRM requirements for SDT in INACTIVE State |
ZTE |
R4-2202711 |
Draft CR TA validation for Small Data Transmissions |
Nokia |
R4-2202712 |
Draft CR to TS 38.133: Requirements on UE synchronization for SDT |
Ericsson |
R4-2202713 |
CR on UL timing requirements for SDT |
Huawei |
6.26 |
Support for Multi-SIM devices for LTE/NR |
|
R4-2202579 |
Email discussion summary for [101-bis-e][228] LTE_NR_MUSIM |
Moderator (Vivo) |
R4-2202745 |
Email discussion summary for [101-bis-e][228] LTE_NR_MUSIM |
Moderator (Vivo) |
6.26.1 |
General and work plan |
|
R4-2200669 |
Work plan for Multi-SIM devices for LTE/NR |
vivo |
R4-2201210 |
Further LS response on gap handling for MUSIM |
Ericsson |
R4-2202760 |
draftCR on New gap pattern for MUSIM |
Ericsson |
6.26.2 |
RRM core requirements |
|
R4-2200386 |
On MUSIM requirements |
vivo |
R4-2200402 |
Draft CR for introducing gap patterns for MUSIM |
vivo |
R4-2200428 |
Discussion on MUSIM requirements |
Charter Communications, Inc |
R4-2200529 |
Discussion on MUSIM RRM impacts |
Intel Corporation |
R4-2200672 |
Discussion on RAN2 LS (R2-2108861) on gap handling for MUSIM |
Apple |
R4-2200683 |
Discussion on the gap pattern for MUSIM |
Xiaomi |
R4-2201169 |
Discussion on RRM core requirements for Multi-SIM devices |
OPPO |
R4-2201211 |
New gap pattern for MUSIM |
Ericsson |
R4-2201212 |
draftCR on New gap pattern for MUSIM |
Ericsson |
R4-2201646 |
Discussion on gap patterns for MU-SIM |
Huawei, Hisilicon |
R4-2201647 |
CR on measurement gap patterns for MUSIM |
Huawei, Hisilicon |
R4-2201698 |
Requirements for MUSIM switching gaps |
Nokia, Nokia Shanghai Bell |
R4-2201699 |
Introduction of MUSIM switching gaps |
Nokia, Nokia Shanghai Bell |
R4-2202714 |
WF on R17 Support for Multi-SIM devices for LTENR |
vivo |
7.1.1 |
Maintenance on objectives 1~6 |
|
R4-2200452 |
TP to TR 38.884 on release independence applicability of test method enhancements |
Apple |
7.1.2.1 |
General |
|
R4-2202978 |
Email discussion summary for [101-bis-e][327] FR2_enhTestMethods |
Moderator (Intel) |
R4-2203078 |
TP to TR 38.884 on extension of NR test methods to FR2-2 |
Intel Corporation |
R4-2203079 |
WF on OTA test methods for FR2-2 |
Intel Corporation |
R4-2203120 |
Email discussion summary for [101-bis-e][327] FR2_enhTestMethods |
Moderator (Intel) |
R4-2203128 |
Draft TR 38.884 v1.3.0: Study on enhanced test methods for FR2 NR Ues |
Apple, vivo, Intel |
7.1.2.1.2 |
UE types |
|
R4-2201921 |
On Vehicular UEs |
Keysight Technologies UK Ltd |
7.1.2.1.4 |
Others |
|
R4-2201873 |
TP to TR 38.884 on extension of NR test methods to FR2-2 |
Intel Corporation |
R4-2201927 |
UE types and permitted methods for FR2-2 |
Intel Corporation |
7.1.2.2 |
Test methodology for UE RF |
|
R4-2201990 |
Issues with MIMO EVM Measurement Using the Pseudo-Inverse |
Lenovo, Motorola Mobility |
7.1.2.3 |
Test methodology for RRM |
|
R4-2201874 |
NR FR2-2 OTA test methods for RRM |
Intel Corporation |
7.1.2.4 |
Test methodology for UE demodulation and CSI |
|
R4-2200907 |
On permitted test methods for demodulation in FR2-2 |
Apple |
R4-2201875 |
NR FR2-2 OTA test methods for UE demodulation |
Intel Corporation |
7.2 |
Study on Efficient utilization of licensed spectrum that is not aligned with existing NR channel bandwidths |
|
R4-2202233 |
Email discussion summary for [101-bis-e][133] FS_NR_eff_BW_util |
Moderator (Ericsson) |
R4-2202333 |
Email discussion summary for [101-bis-e][133] FS_NR_eff_BW_util |
Moderator (Ericsson) |
7.2.1 |
General and TR |
|
R4-2201485 |
draft TR 38.844 v0.0.6 |
Ericsson |
R4-2201794 |
Revision on TR 38.344 Section 6.2.3 |
ZTE Wistron Telecom AB |
R4-2202046 |
TP for TR 38.844: Proposal for n12 and n85 |
T-Mobile USA |
R4-2202374 |
TP to TR 38.844: Section 6.1.2 Signalling for Larger Channel BW Approach |
Ericsson |
R4-2202375 |
TP to TR 38.844: Wider CBW method |
Intel Corporation |
R4-2202376 |
TP with corrections for overlapping channels from the network |
Apple |
R4-2202377 |
On overlapping CBWs from Network perspective |
Huawei, HiSilicon |
R4-2202378 |
TP to TR 38.844: on combined UE CBW (one cell) – signalling aspects |
Nokia, Nokia Shanghai Bell |
R4-2202380 |
TP to TR 38.844: Clause 6.7.x RAN4 standard impact identification |
Qualcomm |
R4-2202381 |
TP to TR 38.844: Clause 6.1.2 Signalling and configuration aspects |
China Telecom |
R4-2202382 |
TP to TR 38.844: Clause 7 |
Qualcomm |
R4-2202416 |
TP for TR 38.844: Proposal for n12 and n85 |
T-Mobile USA |
R4-2202423 |
TP to TR 38.844: Wider CBW method |
Intel Corporation |
7.2.2 |
Evaluation of use of larger channel bandwidths than licensed bandwidth |
|
R4-2200913 |
Discussion on the widerCBW approach |
China Telecom |
R4-2201509 |
On the applicability of wider channel bandwidth |
Huawei, HiSilicon |
7.2.2.1 |
Channel filter assumptions and RB blanking with impacts on UE (ACS, blocking) |
|
R4-2200911 |
Further input on performance when using the next larger channel |
Apple |
7.2.2.2 |
Signaling and configuration (RAN1/RAN2 impacts) aspects |
|
R4-2201486 |
TP to TR 38.844: Section 6.1.2 Signalling for Larger Channel BW Approach |
Ericsson |
R4-2201795 |
Further discussion on the WiderCBW approach |
ZTE Wistron Telecom AB |
R4-2201880 |
Views on signalling for Wider CBW method |
Intel Corporation |
7.2.2.3 |
Other aspects such as detailed solution, complexity, legacy UE, etc |
|
R4-2201995 |
On wider CBW open issues |
Nokia, Nokia Shanghai Bell |
7.2.3.1 |
Overlapping CBWs from network perspective |
|
R4-2200912 |
Further corrections to the solution based on overlapping channels from the network perspective |
Apple |
R4-2201510 |
Signaling aspect for overlapping from network perspective |
Huawei, HiSilicon |
R4-2201511 |
On overlapping CBWs from Network perspective |
Huawei, HiSilicon |
7.3.2.1.1 |
Signaling and configuration (RAN1/RAN2 impacts) aspects |
|
R4-2201881 |
Views on Signalling for Overlapping CBW from Network Perspective |
Intel Corporation |
7.3.2.1.2 |
Other aspects such as detailed solution, complexity, legacy UE, etc |
|
R4-2201882 |
Views on BS TX Channel BW Filters for Overlapping CBW |
Intel Corporation |
7.2.3.2.1 |
Signaling and configuration (RAN1/RAN2 impacts) aspects |
|
R4-2201488 |
TP to TR 38.844: Section 6.1.2 Signalling for Overlapping Channel BW from UE perspective Approach |
Ericsson |
R4-2201883 |
Views on Overlapping UE CBWs method |
Intel Corporation |
R4-2201993 |
TP to TR 38.844: on combined UE CBW (one cell) – signalling aspects |
Nokia, Nokia Shanghai Bell |
7.2.3.2.2 |
Other aspects such as detailed solution, complexity, legacy UE, etc |
|
R4-2201994 |
On combined UE CBW (one cell) gNB channel filter and UE requirements |
Nokia, Nokia Shanghai Bell |
7.2.3.3.1 |
Signaling and configuration (RAN1/RAN2 impacts) aspects |
|
R4-2201487 |
TP to TR 38.844: Section 6.1.2 Signalling for Overlapping CA Approach |
Ericsson |
R4-2201884 |
Views on Overlapping CA method |
Intel Corporation |
R4-2202379 |
TP to TR 38.844: Section 6.1.2 Signalling for Overlapping CA Approach |
Ericsson |
7.2.3.3.2 |
Other aspects such as detailed solution, complexity, legacy UE, etc |
|
R4-2201333 |
TP to TR 38.844: Section 6.5.1 Overlapping CA (two cells) |
Ericsson |
R4-2201512 |
RF requirements for overlapping CA |
Huawei, HiSilicon |
7.2.3.4 |
Overall method comparisons |
|
R4-2200817 |
Discussion on overall method comparisons for irregular bandwidth |
CMCC |
R4-2200921 |
Considerations for wider CBW and overlapping UE CBW solutions |
China Telecom |
R4-2201264 |
Comparison of Different Schemes |
Qualcomm Incorporated |
R4-2201492 |
Comparison Between Methods for Irregular BWs |
Ericsson |
R4-2201513 |
Overall method comparisons |
Huawei, HiSilicon |
R4-2201885 |
TP to TR 38.844: Wider CBW method |
Intel Corporation |
R4-2201992 |
Irregular bandwidth – comparison between options |
MediaTek (Chengdu) Inc. |
7.3 |
Study on band combination handling in RAN4 |
|
R4-2202234 |
Email discussion summary for [101-bis-e][134] FS_BC_handling |
Moderator (ZTE) |
R4-2202334 |
Email discussion summary for [101-bis-e][134] FS_BC_handling |
Moderator (ZTE) |
7.3.1 |
General and TR |
|
R4-2200613 |
TR 38.862 V050 Band combination handling |
ZTE Corporation |
R4-2200614 |
Motivation on further study on band combination handling in Rel-18 |
ZTE Corporation |
R4-2200615 |
Draft New SID on further study on band combination handling in RAN4 |
ZTE Corporation |
R4-2202383 |
WF on simplification for DC configuration table in Rel-18 |
ZTE Corporation |
R4-2202384 |
TP to TR38.862 on introduction to BCS4 and BCS5 |
ZTE Corporation, Xiaomi |
7.3.2 |
Information of rules and guidelines of specifying band combinations (TP format, notation, band configurations, BCS) |
|
R4-2200553 |
Adding contributions not for block approval |
Skyworks Solutions Inc. |
R4-2200618 |
TP to TR38.862 on introdution to BCS4 and BCS5 |
ZTE Corporation, Xiaomi |
R4-2202385 |
TP to TR38.862 on introduction to BCS4 and BCS5 |
ZTE Corporation, Xiaomi |
7.3.3.1 |
Optimization of delta TIB and delta RIB |
|
R4-2200617 |
Band category for rule based approach for delta TIB and RIB |
ZTE Corporation |
R4-2200705 |
Statistics of dTib and dRib |
Nokia, Nokia Shanghai Bell |
7.3.3.2 |
Optimizations for other redundancy |
|
R4-2200616 |
TP to TR38.862 on simplification for DC configuration table in Rel-18 |
ZTE Corporation |
7.4 |
Optimizations of pi/2 BPSK uplink power in NR |
|
R4-2202235 |
Email discussion summary for [101-bis-e][135] FS_NR_Opt_pi2BPSK |
Moderator (Qualcomm) |
R4-2202335 |
Email discussion summary for [101-bis-e][135] FS_NR_Opt_pi2BPSK |
Moderator (Qualcomm) |
7.4.1 |
General and TR |
|
R4-2200506 |
TR skeleton for SI on optimizations of pi_2 BPSK uplink power |
Qualcomm Incorporated |
R4-2200507 |
TP for Pi/2 BPSK study item for TR38.868 |
Qualcomm Incorporated |
R4-2202386 |
WF on optimizations of Pi/2 BPSK UL power in NR and agreements |
Huawei, HiSilicon, Qualcomm Inc. |
R4-2202387 |
TP for Pi/2 BPSK study item for TR38.868 |
Qualcomm Incorporated |
7.4.2 |
UE Tx power and related issues |
|
R4-2200443 |
MPR region proposal for PI/2 BPSK power boosting |
Apple |
R4-2200727 |
Transmitter performance for pi/2 BPSK with spectral shaping |
Nokia, Nokia Shanghai Bell |
R4-2200954 |
Discussion on pi/2 BPSK UE Tx power |
vivo |
R4-2201837 |
On the remaining issues for Pi/2 BPSK Optimisations |
Huawei,HiSilicon |
R4-2201879 |
Pi/2 BPSK combined Tx and Rx Link performance |
Intel Corporation |
R4-2202029 |
PC2 Pi/2 BPSK Power Boosting Measurements |
Skyworks Solutions Inc. |
7.4.3 |
Evaluation of filter requirements applicable to identified new UE power capability |
|
R4-2200511 |
Spectral flatness requirements |
Qualcomm Incorporated |
R4-2200728 |
Shaping filter characteristics including transmitter and link performance |
Nokia, Nokia Shanghai Bell |
7.4.4 |
Link level simulations |
|
R4-2200726 |
Receiver performance for pi/2 BPSK with spectral shaping |
Nokia, Nokia Shanghai Bell |
R4-2200955 |
Link level Simulation results for pi/2 BPSK |
vivo |
7.4.6 |
Identify RAN4 requirements |
|
R4-2200729 |
Identify?potential changes for?RAN4 requirements |
Nokia, Nokia Shanghai Bell |
8.1.2 |
UE RF without specific issues |
|
R4-2200349 |
TP to TR 36.717-02-01: CA_2-38 |
Nokia, Nokia Shanghai Bell |
R4-2201911 |
TP for TR 36.717-02-01 to include CA_30A-48A |
Ericsson, AT&T |
R4-2201912 |
TP for TR 36.717-02-02 to include CA_30A-48A |
Ericsson, AT&T |
R4-2201914 |
draft CR 36101 to add CA_2A-2A-46E |
Ericsson, AT&T |
R4-2202240 |
TP for TR 36.717-02-01 to include CA_30A-48A |
Ericsson, AT&T |
R4-2202241 |
TP for TR 36.717-02-02 to include CA_30A-48A |
Ericsson, AT&T |
8.2.2 |
UE RF without specific issues |
|
R4-2200350 |
TP to TR 36.717-03-01: CA_2-7-38 |
Nokia, Nokia Shanghai Bell |
R4-2200707 |
DraftCR 36.101: Addition CA_5A-7A-7A-28A |
Nokia, Telefonica |
R4-2201915 |
draft CR 36101 to add CA_2A-2A-29A-66A |
Ericsson, AT&T |
8.3 |
LTE inter-band Carrier Aggregation for x bands DL (x=4, 5) with 1 band UL |
|
R4-2202236 |
Email discussion summary for [101-bis-e][136] LTE_Baskets |
Moderator (Ericsson) |
8.3.1 |
UE RF with 4 LTE bands CA |
|
R4-2200708 |
DraftCR 36.101: Addition CA_1A-5A-7A-7A-28A |
Nokia, Telefonica |
R4-2200709 |
DraftCR 36.101: Addition CA_3A-5A-7A-7A-28A |
Nokia, Telefonica |
R4-2201913 |
draft CR 36101 to add CA_2A-2A-29A-30A-66A |
Ericsson, AT&T |
8.3.2 |
UE RF with 5 LTE bands CA |
|
R4-2200710 |
DraftCR 36.101: Addition CA_1A-3A-5A-7A-7A-28A |
Nokia, Telefonica |
8.5 |
LTE inter-band Carrier Aggregation for x bands DL (x= 3, 4, 5) with 2 band UL |
|
R4-2200773 |
TR 36.717-03-02 v0.6.0 TR update for LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics France |
R4-2200775 |
Revised WID on LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL in Rel-17 |
LG Electronics France |
R4-2200776 |
Introduction of LTE-A inter-band CA for x bands (x=3,4,5) DL with 2 bands UL to TS36.101 |
LG Electronics France |
8.7.2 |
Others |
|
R4-2201716 |
AMPR simulation results for Cat-M1 for B48 |
Ericsson |
8.8 |
Upper 700MHz A Block new E-UTRA band in US |
|
R4-2200766 |
TR skeleton for TR 36.779 |
Puloli |
R4-2202237 |
Email discussion summary for [101-bis-e][137] LTE_Upper_700MHz |
Moderator (Huawei) |
R4-2202337 |
Email discussion summary for [101-bis-e][137] LTE_Upper_700MHz |
Moderator (Huawei) |
8.8.1 |
General |
|
R4-2200765 |
Work plan for LTE_upper_700MHz_A WI |
Puloli |
R4-2200771 |
TP to TR 36.779 on Frequency band arrangements and regulatory background |
Puloli |
R4-2200772 |
TP to TR 36.779 on Operating band, channel bandwidths, channel numbering |
Puloli |
R4-2202025 |
Draft CR to TS 36.104: exemplary implementation of LTE_upper_700MHz_A band |
Huawei |
R4-2202388 |
WF on the remaining RF issues for upper 700MHz A block E-UTRA band |
Huawei |
R4-2202389 |
Draft CR to TS 36.101: Introduction of upper 700MHz A block into TS 36.101 |
Puloli |
R4-2202390 |
Work plan for LTE_upper_700MHz_A WI |
Puloli |
R4-2202391 |
TP to TR 36.779 on Frequency band arrangements and regulatory background |
Puloli |
R4-2202392 |
TP to TR 36.779 on Operating band, channel bandwidths, channel numbering |
Puloli |
8.8.2 |
Study for co-existence requirements |
|
R4-2202024 |
Further discussion on the BS RF requirements for LTE_upper_700MHz_A |
Huawei |
8.8.3 |
UE RF requirements |
|
R4-2200004 |
Introduction of upper 700MHz A block into TS 36.101 |
Puloli |
R4-2200774 |
TP to TR 36.779 on Analysis on UE requirements for upper 700MHz A block |
Puloli |
R4-2200790 |
draftCR to TS 36.101: Introduction of upper 700MHz A block |
Puloli |
R4-2202393 |
WF on the remaining RF issues for upper 700MHz A block E-UTRA band |
Huawei |
8.8.4 |
BS RF requirements |
|
R4-2200457 |
draft CR on introduction of upper 700MHz A block for 36.104 |
Baicells |
R4-2200458 |
draft CR on introduction of upper 700MHz A block for 37.104 |
Baicells |
R4-2200459 |
draft CR on introduction of upper 700MHz A block for 37.105 |
Baicells |
R4-2200460 |
draft CR on introduction of upper 700MHz A block for 38.104 |
Baicells |
R4-2200461 |
TP to TR 36.779 on BS aspect issues |
Baicells |
R4-2201071 |
TP to TR 36.779 on Analysis on BS requirements for upper 700MHz A block |
Baicells |
R4-2202394 |
draft CR on introduction of upper 700MHz A block for 36.104 |
Baicells |
R4-2202395 |
draft CR on introduction of upper 700MHz A block for 37.104 |
Baicells |
R4-2202396 |
draft CR on introduction of upper 700MHz A block for 37.105 |
Baicells |
R4-2202397 |
draft CR on introduction of upper 700MHz A block for 38.104 |
Baicells |
R4-2202398 |
TP to TR 36.779 on Analysis on BS requirements for upper 700MHz A block |
Baicells |
8.9.2.1 |
BS RF requirements |
|
R4-2200415 |
Proposals on BS RF requirements for support of 16QAM in NB-IoT |
Nokia, Nokia Shanghai Bell |
R4-2201714 |
BS RF impact analysis on R17 NB_IoT |
Ericsson |
R4-2201831 |
Remaining issues for NB-IoT 16QAM BS RF requirements |
Huawei,HiSilicon |
R4-2201832 |
Draft CR to TS36104 Addition of NB-IoT 16QAM |
Huawei,HiSilicon |
R4-2201833 |
Draft CR to TS36141 Addition of NB-IoT 16QAM |
Huawei,HiSilicon |
R4-2202296 |
Draft CR to TS36141 Addition of NB-IoT 16QAM |
Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
8.9.3.1 |
UE RF requirements |
|
R4-2201287 |
On max power reduction for PRACH, PUCCH, and full-PRB PUSCH |
Sony |
R4-2201715 |
RF impact analysis on R17 eMTC WID |
Ericsson |
8.9.4 |
RRM core requirements |
|
R4-2202580 |
Email discussion summary for [101-bis-e][229] NB_IOTenh4_LTE_eMTC6_RRM |
Moderator (Huawei) |
R4-2202715 |
WF on RRM requirements for Rel-17 NB-IoT and LTE-MTC |
Huawei, HiSilicon |
R4-2202716 |
Draft Big CR on RRM requirements for Rel-17 NB-IoT and LTE-MTC |
Huawei, Hisilicon |
R4-2202746 |
Email discussion summary for [101-bis-e][229] NB_IOTenh4_LTE_eMTC6_RRM |
Moderator (Huawei) |
R4-2202764 |
WF on RRM requirements for Rel-17 NB-IoT and LTE-MTC |
Huawei, HiSilicon |
8.9.4.1 |
Neighbour cell measurement in RRC Connected state for NB-IoT |
|
R4-2200764 |
On NB-IoT neighbor cell measurements in RRC_CONNECTED |
Qualcomm Incorporated |
R4-2201208 |
Discussion on RRM requirements for Rel-17 NB-IoT |
Huawei, Hisilicon |
R4-2201437 |
Draft CR on including channel quality table for 16 QAM for Rel-17 NB-IoT |
Huawei, Hisilicon |
R4-2201866 |
Discussions on remaining issues of RRM requirements for NB-IoT |
Ericsson |
R4-2202717 |
Draft CR on including channel quality table for 16 QAM for Rel-17 NB-IoT |
Huawei, Hisilicon |
8.9.5 |
Others |
|
R4-2201431 |
Introduction of channel quality report table for NB-IoT supporting 16QAM |
Ericsson |
8.9.6 |
Demodulation requirements |
|
R4-2202979 |
Email discussion summary for [101-bis-e][323] NB-IOT_MTC_Demod_NWM |
Moderator (Huawei) |
R4-2203041 |
WF on Rel-17 NB-IOT and eMTC performance requirements |
Huawei |
R4-2203121 |
Email discussion summary for [101-bis-e][323] NB-IOT_MTC_Demod_NWM |
Moderator (Huawei) |
8.9.6.2.1 |
UE demodulation requirements |
|
R4-2200763 |
On UE demodulation requirements for 16-QAM NB-IoT |
Qualcomm Incorporated |
R4-2200995 |
Discussion on UE demodulation requirements for additional enhancements of NB-IoT |
Huawei,HiSilicon |
R4-2201432 |
View on Rel-17 NB-IoT UE demodulation requirements |
Ericsson |
8.9.6.2.2 |
BS demodulation requirements |
|
R4-2200751 |
View on demodulation requirement for Rel-17 NB-IoT |
Samsung |
R4-2200996 |
Discussion on BS demodulation requirements for additional enhancements of NB-IoT |
Huawei,HiSilicon |
R4-2201433 |
View on Rel-17 NB-IoT BS demodulation requirements |
Ericsson |
R4-2201984 |
Discussion on BS demodulation requirements for Additional enhancements for NB-IoT |
Nokia, Nokia Shanghai Bell |
8.9.6.3 |
Demodulation requirements for MTC |
|
R4-2200750 |
View on demodulation requirement for Rel-17 eMTC |
Samsung |
R4-2200997 |
Discussion on UE demodulation requirements for additional enhancements of LTE-MTC |
Huawei,HiSilicon |
R4-2201434 |
View on Rel-17 LTE-MTC demodulation requirements |
Ericsson |
9.1 |
R17 related |
|
R4-2202238 |
Email discussion summary for [101-bis-e][138] NR_reply_LS_UE_RF |
Moderator (Apple) |
R4-2202338 |
Email discussion summary for [101-bis-e][138] NR_reply_LS_UE_RF |
Moderator (Apple) |
R4-2202399 |
Response LS to RAN5 on LTE REFSENS Exceptions Simplification |
Huawei, HiSilicon |
9.1.1 |
LS reply for beam correspondence with SDT in RRC_INACTIVE |
|
R4-2200252 |
Discussion on RAN2 LS (R2-2108861) on gap handling for MUSIM |
Apple |
R4-2201484 |
Discussion on reply LS on Beam correspondence with Small Data Transmission in Inactive State |
ZTE Corporation |
R4-2201973 |
On beam correspondence requirements and SDT |
Qualcomm Incorporated |
9.1.2 |
RAN5 response LS on LTE REFSENS exception simplification (R5-215803) |
|
R4-2201247 |
Discussion and draft LS on LTE REFSENS exception simplification |
Huawei, HiSilicon |
9.1.3 |
Others |
|
R4-2201277 |
R17 FR2 power control for NR-DC and draft LS |
OPPO |
R4-2201339 |
Discussion on reply LS on configuration of p-MaxEUTRA and p-NR-FR1 |
ZTE Corporation |
R4-2201477 |
Support of ATG for 5G Advanced |
ZTE Corporation |
R4-2201478 |
Motivation on study on NR NTN RF requirement for coexistence with TN standalone NB-IoT |
ZTE Corporation |
R4-2201479 |
New SI proposal: Study on NR NTN RF requirement for coexistence with TN standalone NB-IoT |
ZTE Corporation |
R4-2201480 |
Views on NR UE RF enhancement in Rel-18 |
ZTE Corporation |
R4-2201481 |
Views on NR BS RF enhancement in Rel-18 |
ZTE Corporation |
R4-2201482 |
Views on NR UE RRM enhancement in Rel-18 |
ZTE Corporation |
R4-2201483 |
Motivation on the support of CRS-IM for Redcap UE |
ZTE Corporation |
R4-2201697 |
Incoming LS from RAN2 on L3 filter |
Nokia, Nokia Shanghai Bell |
R4-2201974 |
On reply to RAN5 on FR2 requirement applicability over ETC |
Qualcomm Incorporated |
10 |
Any other business |
|
R4-2200172 |
Motivation for new WI on air-to-ground network for NR |
CMCC |
R4-2200173 |
New WID on air-to-ground network for NR |
CMCC |
R4-2200174 |
Motivation for new WID on Home Base Station for NR |
CMCC |
R4-2200175 |
New WID on Home Base Station for NR |
CMCC |
R4-2200287 |
Rel-18 proposal on FR2 coverage/performance enhancements |
Apple |
R4-2200299 |
Motivation paper for R18 RRM enhancement |
Apple |
R4-2200451 |
Views on handling ETC applicability to FR2 UE RF requirements |
Apple |
R4-2200545 |
Views on RAN4 Rel-18 scope |
Intel Corporation |
R4-2200546 |
Views on RAN4 Rel-18: FR2 multi-beam reception |
Intel Corporation |
R4-2200547 |
Views on RAN4 Rel-18: RRM enhancements |
Intel Corporation |
R4-2200548 |
Views on RAN4 Rel-18: Demodulation enhancements |
Intel Corporation |
R4-2200549 |
Draft New WID: Requirements for NR FR2 UEs with multi-Rx chain DL reception |
Intel Corporation |
R4-2200550 |
Draft New WID: NR and MR-DC RRM requirements enhancements |
Intel Corporation |
R4-2200551 |
Draft New WID: NR and MR-DC Measurement Gap further enhancements |
Intel Corporation |
R4-2200552 |
Draft New WID: NR demodulation requirements enhancements |
Intel Corporation |
R4-2201193 |
[Draft] WID on FR2 RRM requirements evaluation |
Huawei, Hisilicon |
R4-2201280 |
R18 Motivation of 3Tx handheld UE |
OPPO |
R4-2201281 |
R18 New WID on 3Tx handheld UE for NR |
OPPO |
R4-2201360 |
Motivation on basket WID on 4Rx and 8Rx bands |
ZTE Corporation |
R4-2201361 |
New WID on 4Rx_8Rx support for NR bands |
ZTE,China Telecom |
R4-2201648 |
Motivation for FR2 RRM requirement enhancement |
Huawei, Hisilicon |
R4-2201650 |
Views on small A-MPR for Rel-18 RAN4 led WI |
Nokia, Nokia Shanghai Bell |
R4-2201653 |
New WID on Low MSD for CA and DC band combinations |
Nokia, Nokia Shanghai Bell |
R4-2201675 |
Motivation of new WID on High Altitude Platform Station (HAPS) for NR |
China Unicom |
R4-2201677 |
Rel-18 Draft New WID on High Altitude Platform Station (HAPS) for NR |
China Unicom |
R4-2201678 |
Draft Rel-18 new basket WID on high power UE (power class 2) for NR FDD band |
China Unicom |
R4-2201679 |
Draft Rel-18 new basket WID on High power UE (power class 1.5) for NR inter-band CA with 2 UL bands |
China Unicom |
R4-2202047 |
R18 New WID on NR MIMO OTA |
CAICT, OPPO |
R4-2202050 |
R18 New WID on FR1 TRP TRS |
OPPO, CAICT |
11 |
Close of the E-meeting |
|
R4-2202054 |
(reserved) |
ETSI MCC |
R4-2202055 |
(reserved) |
ETSI MCC |
R4-2202056 |
(reserved) |
ETSI MCC |
R4-2202057 |
(reserved) |
ETSI MCC |
R4-2202058 |
(reserved) |
ETSI MCC |
R4-2202059 |
(reserved) |
ETSI MCC |
R4-2202060 |
(reserved) |
ETSI MCC |
R4-2202061 |
(reserved) |
ETSI MCC |
R4-2202062 |
(reserved) |
ETSI MCC |
R4-2202063 |
(reserved) |
ETSI MCC |
R4-2202064 |
(reserved) |
ETSI MCC |
R4-2202065 |
(reserved) |
ETSI MCC |
R4-2202066 |
(reserved) |
ETSI MCC |
R4-2202067 |
(reserved) |
ETSI MCC |
R4-2202068 |
(reserved) |
ETSI MCC |
R4-2202069 |
(reserved) |
ETSI MCC |
R4-2202070 |
(reserved) |
ETSI MCC |
R4-2202071 |
(reserved) |
ETSI MCC |
R4-2202072 |
(reserved) |
ETSI MCC |
R4-2202073 |
(reserved) |
ETSI MCC |
R4-2202074 |
(reserved) |
ETSI MCC |
R4-2202075 |
(reserved) |
ETSI MCC |
R4-2202076 |
(reserved) |
ETSI MCC |
R4-2202077 |
(reserved) |
ETSI MCC |
R4-2202078 |
(reserved) |
ETSI MCC |
R4-2202079 |
(reserved) |
ETSI MCC |
R4-2202080 |
(reserved) |
ETSI MCC |
R4-2202081 |
(reserved) |
ETSI MCC |
R4-2202082 |
(reserved) |
ETSI MCC |
R4-2202083 |
(reserved) |
ETSI MCC |
R4-2202084 |
(reserved) |
ETSI MCC |
R4-2202085 |
(reserved) |
ETSI MCC |
R4-2202086 |
(reserved) |
ETSI MCC |
R4-2202087 |
(reserved) |
ETSI MCC |
R4-2202088 |
(reserved) |
ETSI MCC |
R4-2202089 |
(reserved) |
ETSI MCC |
R4-2202090 |
(reserved) |
ETSI MCC |
R4-2202091 |
(reserved) |
ETSI MCC |
R4-2202092 |
(reserved) |
ETSI MCC |
R4-2202093 |
(reserved) |
ETSI MCC |
R4-2202094 |
(reserved) |
ETSI MCC |
R4-2202095 |
(reserved) |
ETSI MCC |
R4-2202096 |
(reserved) |
ETSI MCC |
R4-2202097 |
(reserved) |
ETSI MCC |
R4-2202098 |
(reserved) |
ETSI MCC |
R4-2202099 |
(reserved) |
ETSI MCC |
R4-2202100 |
(reserved) |
ETSI MCC |
R4-2202101 |
(reserved) |
ETSI MCC |
R4-2202102 |
(reserved) |
ETSI MCC |
R4-2202103 |
(reserved) |
ETSI MCC |
R4-2202104 |
(reserved) |
ETSI MCC |
R4-2202105 |
(reserved) |
ETSI MCC |
R4-2202106 |
(reserved) |
ETSI MCC |
R4-2202107 |
(reserved) |
ETSI MCC |
R4-2202108 |
(reserved) |
ETSI MCC |
R4-2202109 |
(reserved) |
ETSI MCC |
R4-2202110 |
(reserved) |
ETSI MCC |
R4-2202111 |
(reserved) |
ETSI MCC |
R4-2202112 |
(reserved) |
ETSI MCC |
R4-2202113 |
(reserved) |
ETSI MCC |
R4-2202114 |
(reserved) |
ETSI MCC |
R4-2202115 |
(reserved) |
ETSI MCC |
R4-2202116 |
(reserved) |
ETSI MCC |
R4-2202117 |
(reserved) |
ETSI MCC |
R4-2202118 |
(reserved) |
ETSI MCC |
R4-2202119 |
(reserved) |
ETSI MCC |
R4-2202120 |
(reserved) |
ETSI MCC |
R4-2202121 |
(reserved) |
ETSI MCC |
R4-2202122 |
(reserved) |
ETSI MCC |
R4-2202123 |
(reserved) |
ETSI MCC |
R4-2202124 |
(reserved) |
ETSI MCC |
R4-2202125 |
(reserved) |
ETSI MCC |
R4-2202126 |
(reserved) |
ETSI MCC |
R4-2202127 |
(reserved) |
ETSI MCC |
R4-2202128 |
(reserved) |
ETSI MCC |
R4-2202129 |
(reserved) |
ETSI MCC |
R4-2202130 |
(reserved) |
ETSI MCC |
R4-2202131 |
(reserved) |
ETSI MCC |
R4-2202132 |
(reserved) |
ETSI MCC |
R4-2202133 |
(reserved) |
ETSI MCC |
R4-2202134 |
(reserved) |
ETSI MCC |
R4-2202135 |
(reserved) |
ETSI MCC |
R4-2202136 |
(reserved) |
ETSI MCC |
R4-2202137 |
(reserved) |
ETSI MCC |
R4-2202138 |
(reserved) |
ETSI MCC |
R4-2202139 |
(reserved) |
ETSI MCC |
R4-2202140 |
(reserved) |
ETSI MCC |
R4-2202141 |
(reserved) |
ETSI MCC |
R4-2202142 |
(reserved) |
ETSI MCC |
R4-2202143 |
(reserved) |
ETSI MCC |
R4-2202144 |
(reserved) |
ETSI MCC |
R4-2202145 |
(reserved) |
ETSI MCC |
R4-2202146 |
(reserved) |
ETSI MCC |
R4-2202147 |
(reserved) |
ETSI MCC |
R4-2202148 |
(reserved) |
ETSI MCC |
R4-2202149 |
(reserved) |
ETSI MCC |
R4-2202150 |
(reserved) |
ETSI MCC |
R4-2202151 |
(reserved) |
ETSI MCC |
R4-2202152 |
(reserved) |
ETSI MCC |
R4-2202306 |
(reserved) |
Main Session |
R4-2202307 |
(reserved) |
Main Session |
R4-2202336 |
(reserved) |
Main Session |
R4-2202426 |
(reserved) |
Main Session |
R4-2202427 |
(reserved) |
Main Session |
R4-2202428 |
(reserved) |
Main Session |
R4-2202429 |
(reserved) |
Main Session |
R4-2202430 |
(reserved) |
Main Session |
R4-2202431 |
(reserved) |
Main Session |
R4-2202432 |
(reserved) |
Main Session |
R4-2202433 |
(reserved) |
Main Session |
R4-2202434 |
(reserved) |
Main Session |
R4-2202435 |
(reserved) |
Main Session |
R4-2202436 |
(reserved) |
Main Session |
R4-2202437 |
(reserved) |
Main Session |
R4-2202438 |
(reserved) |
Main Session |
R4-2202439 |
(reserved) |
Main Session |
R4-2202440 |
(reserved) |
Main Session |
R4-2202441 |
(reserved) |
Main Session |
R4-2202442 |
(reserved) |
Main Session |
R4-2202443 |
(reserved) |
Main Session |
R4-2202444 |
(reserved) |
Main Session |
R4-2202445 |
(reserved) |
Main Session |
R4-2202446 |
(reserved) |
Main Session |
R4-2202447 |
(reserved) |
Main Session |
R4-2202448 |
(reserved) |
Main Session |
R4-2202449 |
(reserved) |
Main Session |
R4-2202450 |
(reserved) |
Main Session |
R4-2202451 |
(reserved) |
Main Session |
R4-2202452 |
(reserved) |
Main Session |
R4-2202453 |
(reserved) |
Main Session |
R4-2202454 |
(reserved) |
Main Session |
R4-2202455 |
(reserved) |
Main Session |
R4-2202456 |
(reserved) |
Main Session |
R4-2202457 |
(reserved) |
Main Session |
R4-2202458 |
(reserved) |
Main Session |
R4-2202459 |
(reserved) |
Main Session |
R4-2202460 |
(reserved) |
Main Session |
R4-2202461 |
(reserved) |
Main Session |
R4-2202462 |
(reserved) |
Main Session |
R4-2202463 |
(reserved) |
Main Session |
R4-2202464 |
(reserved) |
Main Session |
R4-2202465 |
(reserved) |
Main Session |
R4-2202466 |
(reserved) |
Main Session |
R4-2202467 |
(reserved) |
Main Session |
R4-2202468 |
(reserved) |
Main Session |
R4-2202469 |
(reserved) |
Main Session |
R4-2202470 |
(reserved) |
Main Session |
R4-2202471 |
(reserved) |
Main Session |
R4-2202472 |
(reserved) |
Main Session |
R4-2202473 |
(reserved) |
Main Session |
R4-2202474 |
(reserved) |
Main Session |
R4-2202475 |
(reserved) |
Main Session |
R4-2202476 |
(reserved) |
Main Session |
R4-2202477 |
(reserved) |
Main Session |
R4-2202478 |
(reserved) |
Main Session |
R4-2202479 |
(reserved) |
Main Session |
R4-2202480 |
(reserved) |
Main Session |
R4-2202481 |
(reserved) |
Main Session |
R4-2202482 |
(reserved) |
Main Session |
R4-2202483 |
(reserved) |
Main Session |
R4-2202484 |
(reserved) |
Main Session |
R4-2202485 |
(reserved) |
Main Session |
R4-2202486 |
(reserved) |
Main Session |
R4-2202487 |
(reserved) |
Main Session |
R4-2202488 |
(reserved) |
Main Session |
R4-2202489 |
(reserved) |
Main Session |
R4-2202490 |
(reserved) |
Main Session |
R4-2202491 |
(reserved) |
Main Session |
R4-2202492 |
(reserved) |
Main Session |
R4-2202493 |
(reserved) |
Main Session |
R4-2202494 |
(reserved) |
Main Session |
R4-2202495 |
(reserved) |
Main Session |
R4-2202496 |
(reserved) |
Main Session |
R4-2202497 |
(reserved) |
Main Session |
R4-2202498 |
(reserved) |
Main Session |
R4-2202499 |
(reserved) |
Main Session |
R4-2202500 |
(reserved) |
Main Session |
R4-2202501 |
(reserved) |
Main Session |
R4-2202502 |
(reserved) |
Main Session |
R4-2202503 |
(reserved) |
Main Session |
R4-2202504 |
(reserved) |
Main Session |
R4-2202505 |
(reserved) |
Main Session |
R4-2202506 |
(reserved) |
Main Session |
R4-2202507 |
(reserved) |
Main Session |
R4-2202508 |
(reserved) |
Main Session |
R4-2202509 |
(reserved) |
Main Session |
R4-2202510 |
(reserved) |
Main Session |
R4-2202511 |
(reserved) |
Main Session |
R4-2202512 |
(reserved) |
Main Session |
R4-2202513 |
(reserved) |
Main Session |
R4-2202514 |
(reserved) |
Main Session |
R4-2202515 |
(reserved) |
Main Session |
R4-2202516 |
(reserved) |
Main Session |
R4-2202517 |
(reserved) |
Main Session |
R4-2202518 |
(reserved) |
Main Session |
R4-2202519 |
(reserved) |
Main Session |
R4-2202520 |
(reserved) |
Main Session |
R4-2202521 |
(reserved) |
Main Session |
R4-2202522 |
(reserved) |
Main Session |
R4-2202523 |
(reserved) |
Main Session |
R4-2202524 |
(reserved) |
Main Session |
R4-2202525 |
(reserved) |
Main Session |
R4-2202526 |
(reserved) |
Main Session |
R4-2202527 |
(reserved) |
Main Session |
R4-2202528 |
(reserved) |
Main Session |
R4-2202529 |
(reserved) |
Main Session |
R4-2202530 |
(reserved) |
Main Session |
R4-2202531 |
(reserved) |
Main Session |
R4-2202532 |
(reserved) |
Main Session |
R4-2202533 |
(reserved) |
Main Session |
R4-2202534 |
(reserved) |
Main Session |
R4-2202535 |
(reserved) |
Main Session |
R4-2202536 |
(reserved) |
Main Session |
R4-2202537 |
(reserved) |
Main Session |
R4-2202538 |
(reserved) |
Main Session |
R4-2202539 |
(reserved) |
Main Session |
R4-2202540 |
(reserved) |
Main Session |
R4-2202541 |
(reserved) |
Main Session |
R4-2202542 |
(reserved) |
Main Session |
R4-2202543 |
(reserved) |
Main Session |
R4-2202544 |
(reserved) |
Main Session |
R4-2202545 |
(reserved) |
Main Session |
R4-2202546 |
(reserved) |
Main Session |
R4-2202547 |
(reserved) |
Main Session |
R4-2202548 |
(reserved) |
Main Session |
R4-2202549 |
(reserved) |
Main Session |
R4-2202550 |
(reserved) |
Main Session |
R4-2202551 |
(reserved) |
Main Session |
R4-2202552 |
(reserved) |
Main Session |
R4-2202783 |
(reserved) |
RRM Session |
R4-2202784 |
(reserved) |
RRM Session |
R4-2202785 |
(reserved) |
RRM Session |
R4-2202786 |
(reserved) |
RRM Session |
R4-2202787 |
(reserved) |
RRM Session |
R4-2202788 |
(reserved) |
RRM Session |
R4-2202789 |
(reserved) |
RRM Session |
R4-2202790 |
(reserved) |
RRM Session |
R4-2202791 |
(reserved) |
RRM Session |
R4-2202792 |
(reserved) |
RRM Session |
R4-2202793 |
(reserved) |
RRM Session |
R4-2202794 |
(reserved) |
RRM Session |
R4-2202795 |
(reserved) |
RRM Session |
R4-2202796 |
(reserved) |
RRM Session |
R4-2202797 |
(reserved) |
RRM Session |
R4-2202798 |
(reserved) |
RRM Session |
R4-2202799 |
(reserved) |
RRM Session |
R4-2202800 |
(reserved) |
RRM Session |
R4-2202801 |
(reserved) |
RRM Session |
R4-2202802 |
(reserved) |
RRM Session |
R4-2202803 |
(reserved) |
RRM Session |
R4-2202804 |
(reserved) |
RRM Session |
R4-2202805 |
(reserved) |
RRM Session |
R4-2202806 |
(reserved) |
RRM Session |
R4-2202807 |
(reserved) |
RRM Session |
R4-2202808 |
(reserved) |
RRM Session |
R4-2202809 |
(reserved) |
RRM Session |
R4-2202810 |
(reserved) |
RRM Session |
R4-2202811 |
(reserved) |
RRM Session |
R4-2202812 |
(reserved) |
RRM Session |
R4-2202813 |
(reserved) |
RRM Session |
R4-2202814 |
(reserved) |
RRM Session |
R4-2202815 |
(reserved) |
RRM Session |
R4-2202816 |
(reserved) |
RRM Session |
R4-2202817 |
(reserved) |
RRM Session |
R4-2202818 |
(reserved) |
RRM Session |
R4-2202819 |
(reserved) |
RRM Session |
R4-2202820 |
(reserved) |
RRM Session |
R4-2202821 |
(reserved) |
RRM Session |
R4-2202822 |
(reserved) |
RRM Session |
R4-2202823 |
(reserved) |
RRM Session |
R4-2202824 |
(reserved) |
RRM Session |
R4-2202825 |
(reserved) |
RRM Session |
R4-2202826 |
(reserved) |
RRM Session |
R4-2202827 |
(reserved) |
RRM Session |
R4-2202828 |
(reserved) |
RRM Session |
R4-2202829 |
(reserved) |
RRM Session |
R4-2202830 |
(reserved) |
RRM Session |
R4-2202831 |
(reserved) |
RRM Session |
R4-2202832 |
(reserved) |
RRM Session |
R4-2202833 |
(reserved) |
RRM Session |
R4-2202834 |
(reserved) |
RRM Session |
R4-2202835 |
(reserved) |
RRM Session |
R4-2202836 |
(reserved) |
RRM Session |
R4-2202837 |
(reserved) |
RRM Session |
R4-2202838 |
(reserved) |
RRM Session |
R4-2202839 |
(reserved) |
RRM Session |
R4-2202840 |
(reserved) |
RRM Session |
R4-2202841 |
(reserved) |
RRM Session |
R4-2202842 |
(reserved) |
RRM Session |
R4-2202843 |
(reserved) |
RRM Session |
R4-2202844 |
(reserved) |
RRM Session |
R4-2202845 |
(reserved) |
RRM Session |
R4-2202846 |
(reserved) |
RRM Session |
R4-2202847 |
(reserved) |
RRM Session |
R4-2202848 |
(reserved) |
RRM Session |
R4-2202849 |
(reserved) |
RRM Session |
R4-2202850 |
(reserved) |
RRM Session |
R4-2202851 |
(reserved) |
RRM Session |
R4-2202852 |
(reserved) |
RRM Session |
R4-2202853 |
(reserved) |
RRM Session |
R4-2202854 |
(reserved) |
RRM Session |
R4-2202855 |
(reserved) |
RRM Session |
R4-2202856 |
(reserved) |
RRM Session |
R4-2202857 |
(reserved) |
RRM Session |
R4-2202858 |
(reserved) |
RRM Session |
R4-2202859 |
(reserved) |
RRM Session |
R4-2202860 |
(reserved) |
RRM Session |
R4-2202861 |
(reserved) |
RRM Session |
R4-2202862 |
(reserved) |
RRM Session |
R4-2202863 |
(reserved) |
RRM Session |
R4-2202864 |
(reserved) |
RRM Session |
R4-2202865 |
(reserved) |
RRM Session |
R4-2202866 |
(reserved) |
RRM Session |
R4-2202867 |
(reserved) |
RRM Session |
R4-2202868 |
(reserved) |
RRM Session |
R4-2202869 |
(reserved) |
RRM Session |
R4-2202870 |
(reserved) |
RRM Session |
R4-2202871 |
(reserved) |
RRM Session |
R4-2202872 |
(reserved) |
RRM Session |
R4-2202873 |
(reserved) |
RRM Session |
R4-2202874 |
(reserved) |
RRM Session |
R4-2202875 |
(reserved) |
RRM Session |
R4-2202876 |
(reserved) |
RRM Session |
R4-2202877 |
(reserved) |
RRM Session |
R4-2202878 |
(reserved) |
RRM Session |
R4-2202879 |
(reserved) |
RRM Session |
R4-2202880 |
(reserved) |
RRM Session |
R4-2202881 |
(reserved) |
RRM Session |
R4-2202882 |
(reserved) |
RRM Session |
R4-2202883 |
(reserved) |
RRM Session |
R4-2202884 |
(reserved) |
RRM Session |
R4-2202885 |
(reserved) |
RRM Session |
R4-2202886 |
(reserved) |
RRM Session |
R4-2202887 |
(reserved) |
RRM Session |
R4-2202888 |
(reserved) |
RRM Session |
R4-2202889 |
(reserved) |
RRM Session |
R4-2202890 |
(reserved) |
RRM Session |
R4-2202891 |
(reserved) |
RRM Session |
R4-2202892 |
(reserved) |
RRM Session |
R4-2202893 |
(reserved) |
RRM Session |
R4-2202894 |
(reserved) |
RRM Session |
R4-2202895 |
(reserved) |
RRM Session |
R4-2202896 |
(reserved) |
RRM Session |
R4-2202897 |
(reserved) |
RRM Session |
R4-2202898 |
(reserved) |
RRM Session |
R4-2202899 |
(reserved) |
RRM Session |
R4-2202900 |
(reserved) |
RRM Session |
R4-2202901 |
(reserved) |
RRM Session |
R4-2202902 |
(reserved) |
RRM Session |
R4-2202903 |
(reserved) |
RRM Session |
R4-2202904 |
(reserved) |
RRM Session |
R4-2202905 |
(reserved) |
RRM Session |
R4-2202906 |
(reserved) |
RRM Session |
R4-2202907 |
(reserved) |
RRM Session |
R4-2202908 |
(reserved) |
RRM Session |
R4-2202909 |
(reserved) |
RRM Session |
R4-2202910 |
(reserved) |
RRM Session |
R4-2202911 |
(reserved) |
RRM Session |
R4-2202912 |
(reserved) |
RRM Session |
R4-2202913 |
(reserved) |
RRM Session |
R4-2202914 |
(reserved) |
RRM Session |
R4-2202915 |
(reserved) |
RRM Session |
R4-2202916 |
(reserved) |
RRM Session |
R4-2202917 |
(reserved) |
RRM Session |
R4-2202918 |
(reserved) |
RRM Session |
R4-2202919 |
(reserved) |
RRM Session |
R4-2202920 |
(reserved) |
RRM Session |
R4-2202921 |
(reserved) |
RRM Session |
R4-2202922 |
(reserved) |
RRM Session |
R4-2202923 |
(reserved) |
RRM Session |
R4-2202924 |
(reserved) |
RRM Session |
R4-2202925 |
(reserved) |
RRM Session |
R4-2202926 |
(reserved) |
RRM Session |
R4-2202927 |
(reserved) |
RRM Session |
R4-2202928 |
(reserved) |
RRM Session |
R4-2202929 |
(reserved) |
RRM Session |
R4-2202930 |
(reserved) |
RRM Session |
R4-2202931 |
(reserved) |
RRM Session |
R4-2202932 |
(reserved) |
RRM Session |
R4-2202933 |
(reserved) |
RRM Session |
R4-2202934 |
(reserved) |
RRM Session |
R4-2202935 |
(reserved) |
RRM Session |
R4-2202936 |
(reserved) |
RRM Session |
R4-2202937 |
(reserved) |
RRM Session |
R4-2202938 |
(reserved) |
RRM Session |
R4-2202939 |
(reserved) |
RRM Session |
R4-2202940 |
(reserved) |
RRM Session |
R4-2202941 |
(reserved) |
RRM Session |
R4-2202942 |
(reserved) |
RRM Session |
R4-2202943 |
(reserved) |
RRM Session |
R4-2202944 |
(reserved) |
RRM Session |
R4-2202945 |
(reserved) |
RRM Session |
R4-2202946 |
(reserved) |
RRM Session |
R4-2202947 |
(reserved) |
RRM Session |
R4-2202948 |
(reserved) |
RRM Session |
R4-2202949 |
(reserved) |
RRM Session |
R4-2202950 |
(reserved) |
RRM Session |
R4-2202951 |
(reserved) |
RRM Session |
R4-2202952 |
(reserved) |
RRM Session |
R4-2202989 |
(reserved) |
BSRF Session |
R4-2202997 |
(reserved) |
BSRF Session |
R4-2203133 |
(reserved) |
BSRF Session |
R4-2203134 |
(reserved) |
BSRF Session |
R4-2203135 |
(reserved) |
BSRF Session |
R4-2203136 |
(reserved) |
BSRF Session |
R4-2203137 |
(reserved) |
BSRF Session |
R4-2203138 |
(reserved) |
BSRF Session |
R4-2203139 |
(reserved) |
BSRF Session |
R4-2203140 |
(reserved) |
BSRF Session |
R4-2203141 |
(reserved) |
BSRF Session |
R4-2203142 |
(reserved) |
BSRF Session |
R4-2203143 |
(reserved) |
BSRF Session |
R4-2203144 |
(reserved) |
BSRF Session |
R4-2203145 |
(reserved) |
BSRF Session |
R4-2203146 |
(reserved) |
BSRF Session |
R4-2203147 |
(reserved) |
BSRF Session |
R4-2203148 |
(reserved) |
BSRF Session |
R4-2203149 |
(reserved) |
BSRF Session |
R4-2203150 |
(reserved) |
BSRF Session |
R4-2203151 |
(reserved) |
BSRF Session |
R4-2203152 |
(reserved) |
BSRF Session |
R4-2203153 |
(reserved) |
BSRF Session |
R4-2203154 |
(reserved) |
BSRF Session |
R4-2203155 |
(reserved) |
BSRF Session |
R4-2203156 |
(reserved) |
BSRF Session |
R4-2203157 |
(reserved) |
BSRF Session |
R4-2203158 |
(reserved) |
BSRF Session |
R4-2203159 |
(reserved) |
BSRF Session |
R4-2203160 |
(reserved) |
BSRF Session |
R4-2203161 |
(reserved) |
BSRF Session |
R4-2203162 |
(reserved) |
BSRF Session |
R4-2203163 |
(reserved) |
BSRF Session |
R4-2203164 |
(reserved) |
BSRF Session |
R4-2203165 |
(reserved) |
BSRF Session |
R4-2203166 |
(reserved) |
BSRF Session |
R4-2203167 |
(reserved) |
BSRF Session |
R4-2203168 |
(reserved) |
BSRF Session |
R4-2203169 |
(reserved) |
BSRF Session |
R4-2203170 |
(reserved) |
BSRF Session |
R4-2203171 |
(reserved) |
BSRF Session |
R4-2203172 |
(reserved) |
BSRF Session |
R4-2203173 |
(reserved) |
BSRF Session |
R4-2203174 |
(reserved) |
BSRF Session |
R4-2203175 |
(reserved) |
BSRF Session |
R4-2203176 |
(reserved) |
BSRF Session |
R4-2203177 |
(reserved) |
BSRF Session |
R4-2203178 |
(reserved) |
BSRF Session |
R4-2203179 |
(reserved) |
BSRF Session |
R4-2203180 |
(reserved) |
BSRF Session |
R4-2203181 |
(reserved) |
BSRF Session |
R4-2203182 |
(reserved) |
BSRF Session |
R4-2203183 |
(reserved) |
BSRF Session |
R4-2203184 |
(reserved) |
BSRF Session |
R4-2203185 |
(reserved) |
BSRF Session |
R4-2203186 |
(reserved) |
BSRF Session |
R4-2203187 |
(reserved) |
BSRF Session |
R4-2203188 |
(reserved) |
BSRF Session |
R4-2203189 |
(reserved) |
BSRF Session |
R4-2203190 |
(reserved) |
BSRF Session |
R4-2203191 |
(reserved) |
BSRF Session |
R4-2203192 |
(reserved) |
BSRF Session |
R4-2203193 |
(reserved) |
BSRF Session |
R4-2203194 |
(reserved) |
BSRF Session |
R4-2203195 |
(reserved) |
BSRF Session |
R4-2203196 |
(reserved) |
BSRF Session |
R4-2203197 |
(reserved) |
BSRF Session |
R4-2203198 |
(reserved) |
BSRF Session |
R4-2203199 |
(reserved) |
BSRF Session |
R4-2203200 |
(reserved) |
BSRF Session |
R4-2203201 |
(reserved) |
BSRF Session |
R4-2203202 |
(reserved) |
BSRF Session |
R4-2203203 |
(reserved) |
BSRF Session |
R4-2203204 |
(reserved) |
BSRF Session |
R4-2203205 |
(reserved) |
BSRF Session |
R4-2203206 |
(reserved) |
BSRF Session |
R4-2203207 |
(reserved) |
BSRF Session |
R4-2203208 |
(reserved) |
BSRF Session |
R4-2203209 |
(reserved) |
BSRF Session |
R4-2203210 |
(reserved) |
BSRF Session |
R4-2203211 |
(reserved) |
BSRF Session |
R4-2203212 |
(reserved) |
BSRF Session |
R4-2203213 |
(reserved) |
BSRF Session |
R4-2203214 |
(reserved) |
BSRF Session |
R4-2203215 |
(reserved) |
BSRF Session |
R4-2203216 |
(reserved) |
BSRF Session |
R4-2203217 |
(reserved) |
BSRF Session |
R4-2203218 |
(reserved) |
BSRF Session |
R4-2203219 |
(reserved) |
BSRF Session |
R4-2203220 |
(reserved) |
BSRF Session |
R4-2203221 |
(reserved) |
BSRF Session |
R4-2203222 |
(reserved) |
BSRF Session |
R4-2203223 |
(reserved) |
BSRF Session |
R4-2203224 |
(reserved) |
BSRF Session |
R4-2203225 |
(reserved) |
BSRF Session |
R4-2203226 |
(reserved) |
BSRF Session |
R4-2203227 |
(reserved) |
BSRF Session |
R4-2203228 |
(reserved) |
BSRF Session |
R4-2203229 |
(reserved) |
BSRF Session |
R4-2203230 |
(reserved) |
BSRF Session |
R4-2203231 |
(reserved) |
BSRF Session |
R4-2203232 |
(reserved) |
BSRF Session |
R4-2203233 |
(reserved) |
BSRF Session |
R4-2203234 |
(reserved) |
BSRF Session |
R4-2203235 |
(reserved) |
BSRF Session |
R4-2203236 |
(reserved) |
BSRF Session |
R4-2203237 |
(reserved) |
BSRF Session |
R4-2203238 |
(reserved) |
BSRF Session |
R4-2203239 |
(reserved) |
BSRF Session |
R4-2203240 |
(reserved) |
BSRF Session |
R4-2203241 |
(reserved) |
BSRF Session |
R4-2203242 |
(reserved) |
BSRF Session |
R4-2203243 |
(reserved) |
BSRF Session |
R4-2203244 |
(reserved) |
BSRF Session |
R4-2203245 |
(reserved) |
BSRF Session |
R4-2203246 |
(reserved) |
BSRF Session |
R4-2203247 |
(reserved) |
BSRF Session |
R4-2203248 |
(reserved) |
BSRF Session |
R4-2203249 |
(reserved) |
BSRF Session |
R4-2203250 |
(reserved) |
BSRF Session |
R4-2203251 |
(reserved) |
BSRF Session |
R4-2203252 |
(reserved) |
BSRF Session |
R4-2203253 |
(reserved) |
BSRF Session |
R4-2203254 |
(reserved) |
BSRF Session |
R4-2203255 |
(reserved) |
BSRF Session |
R4-2203256 |
(reserved) |
BSRF Session |
R4-2203257 |
(reserved) |
BSRF Session |
R4-2203258 |
(reserved) |
BSRF Session |
R4-2203259 |
(reserved) |
BSRF Session |
R4-2203260 |
(reserved) |
BSRF Session |
R4-2203261 |
(reserved) |
BSRF Session |
R4-2203262 |
(reserved) |
BSRF Session |
R4-2203263 |
(reserved) |
BSRF Session |
R4-2203264 |
(reserved) |
BSRF Session |
R4-2203265 |
(reserved) |
BSRF Session |
R4-2203266 |
(reserved) |
BSRF Session |
R4-2203267 |
(reserved) |
BSRF Session |
R4-2203268 |
(reserved) |
BSRF Session |
R4-2203269 |
(reserved) |
BSRF Session |
R4-2203270 |
(reserved) |
BSRF Session |
R4-2203271 |
(reserved) |
BSRF Session |
R4-2203272 |
(reserved) |
BSRF Session |
R4-2203273 |
(reserved) |
BSRF Session |
R4-2203274 |
(reserved) |
BSRF Session |
R4-2203275 |
(reserved) |
BSRF Session |
R4-2203276 |
(reserved) |
BSRF Session |
R4-2203277 |
(reserved) |
BSRF Session |
R4-2203278 |
(reserved) |
BSRF Session |
R4-2203279 |
(reserved) |
BSRF Session |
R4-2203280 |
(reserved) |
BSRF Session |
R4-2203281 |
(reserved) |
BSRF Session |
R4-2203282 |
(reserved) |
BSRF Session |
R4-2203283 |
(reserved) |
BSRF Session |
R4-2203284 |
(reserved) |
BSRF Session |
R4-2203285 |
(reserved) |
BSRF Session |
R4-2203286 |
(reserved) |
BSRF Session |
R4-2203287 |
(reserved) |
BSRF Session |
R4-2203288 |
(reserved) |
BSRF Session |
R4-2203289 |
(reserved) |
BSRF Session |
R4-2203290 |
(reserved) |
BSRF Session |
R4-2203291 |
(reserved) |
BSRF Session |
R4-2203292 |
(reserved) |
BSRF Session |
R4-2203293 |
(reserved) |
BSRF Session |
R4-2203294 |
(reserved) |
BSRF Session |
R4-2203295 |
(reserved) |
BSRF Session |
R4-2203296 |
(reserved) |
BSRF Session |
R4-2203297 |
(reserved) |
BSRF Session |
R4-2203298 |
(reserved) |
BSRF Session |
R4-2203299 |
(reserved) |
BSRF Session |
R4-2203300 |
(reserved) |
BSRF Session |
R4-2203301 |
(reserved) |
BSRF Session |
R4-2203302 |
(reserved) |
BSRF Session |
R4-2203303 |
(reserved) |
BSRF Session |
R4-2203304 |
(reserved) |
BSRF Session |
R4-2203305 |
(reserved) |
BSRF Session |
R4-2203306 |
(reserved) |
BSRF Session |
R4-2203307 |
(reserved) |
BSRF Session |
R4-2203308 |
(reserved) |
BSRF Session |
R4-2203309 |
(reserved) |
BSRF Session |
R4-2203310 |
(reserved) |
BSRF Session |
R4-2203311 |
(reserved) |
BSRF Session |
R4-2203312 |
(reserved) |
BSRF Session |
R4-2203313 |
(reserved) |
BSRF Session |
R4-2203314 |
(reserved) |
BSRF Session |
R4-2203315 |
(reserved) |
BSRF Session |
R4-2203316 |
(reserved) |
BSRF Session |
R4-2203317 |
(reserved) |
BSRF Session |
R4-2203318 |
(reserved) |
BSRF Session |
R4-2203319 |
(reserved) |
BSRF Session |
R4-2203320 |
(reserved) |
BSRF Session |
R4-2203321 |
(reserved) |
BSRF Session |
R4-2203322 |
(reserved) |
BSRF Session |
R4-2203323 |
(reserved) |
BSRF Session |
R4-2203324 |
(reserved) |
BSRF Session |
R4-2203325 |
(reserved) |
BSRF Session |
R4-2203326 |
(reserved) |
BSRF Session |
R4-2203327 |
(reserved) |
BSRF Session |
R4-2203328 |
(reserved) |
BSRF Session |
R4-2203329 |
(reserved) |
BSRF Session |
R4-2203330 |
(reserved) |
BSRF Session |
R4-2203331 |
(reserved) |
BSRF Session |
R4-2203332 |
(reserved) |
BSRF Session |
R4-2203333 |
(reserved) |
BSRF Session |
R4-2203334 |
(reserved) |
BSRF Session |
R4-2203335 |
(reserved) |
BSRF Session |
R4-2203336 |
(reserved) |
BSRF Session |
R4-2203337 |
(reserved) |
BSRF Session |
R4-2203338 |
(reserved) |
BSRF Session |
R4-2203339 |
(reserved) |
BSRF Session |
R4-2203340 |
(reserved) |
BSRF Session |
R4-2203341 |
(reserved) |
BSRF Session |
R4-2203342 |
(reserved) |
BSRF Session |
R4-2203343 |
(reserved) |
BSRF Session |
R4-2203344 |
(reserved) |
BSRF Session |
R4-2203345 |
(reserved) |
BSRF Session |
R4-2203346 |
(reserved) |
BSRF Session |
R4-2203347 |
(reserved) |
BSRF Session |
R4-2203348 |
(reserved) |
BSRF Session |
R4-2203349 |
(reserved) |
BSRF Session |
R4-2203350 |
(reserved) |
BSRF Session |
R4-2203351 |
(reserved) |
BSRF Session |
R4-2203352 |
(reserved) |
BSRF Session |